Difference between revisions of "How to Implement a GFIPM Identity Provider"
From GFIPM Implementation Wiki
Matt.Moyer (Talk | contribs) |
Matt.Moyer (Talk | contribs) |
||
| Line 1: | Line 1: | ||
{| | {| | ||
| − | + | !class="gfipmnav"|Up: [[Welcome to the GFIPM Implementation Portal]] | |
|- | |- | ||
| − | + | !class="gfipmnav"|Next: [[How to Develop a GFIPM Information Sharing Plan for an Identity Provider]] | |
|} | |} | ||
Revision as of 17:47, 3 June 2011
| Up: Welcome to the GFIPM Implementation Portal |
|---|
| Next: How to Develop a GFIPM Information Sharing Plan for an Identity Provider |
A GFIPM Identity Provider (IDP) collects information (typically from an existing identity store) about a local user and generates corresponding user metadata when a user attempts to connect to a local or remote GFIPM Service Provider. This article lists the steps necessary to implement an IDP:
- How to Develop a GFIPM Information Sharing Plan for an Identity Provider
- How to Submit a Request for Federation Membership as a GFIPM Identity Provider
- How to Choose a GFIPM Identity Provider Product
- How to Implement a GFIPM Identity Provider Software Instance
- How to Write a GFIPM Identity Provider Test Plan
- How to Deploy a GFIPM Identity Provider in a Test Environment
- How to Execute a GFIPM Identity Provider Test Plan
- How to Deploy a GFIPM Identity Provider in an Operational Federation
| Up: Welcome to the GFIPM Implementation Portal | Next: How to Develop a GFIPM Information Sharing Plan for an Identity Provider |
|---|
