Difference between revisions of "How to Implement a GFIPM Identity Provider"
From GFIPM Implementation Wiki
Matt.Moyer (Talk | contribs) |
Matt.Moyer (Talk | contribs) |
||
| Line 19: | Line 19: | ||
{| | {| | ||
!class="gfipmnav"|[[Welcome to the GFIPM Implementation Portal|Main Page]] | !class="gfipmnav"|[[Welcome to the GFIPM Implementation Portal|Main Page]] | ||
| − | !class="gfipmnav"|[[Develop a GFIPM Information Sharing Plan for an Identity Provider|Next]] | + | !class="gfipmnav"|[[How to Develop a GFIPM Information Sharing Plan for an Identity Provider|Next]] |
|} | |} | ||
Revision as of 20:19, 2 June 2011
| Main Page | Next |
|---|
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
- Submit a Request for Federation Membership as an Identity Provider
- Choose an IDP Product
- Implement a GFIPM IDP
- Write an IDP Test Plan
- Deploy an IDP in a Test Environment
- Execute an IDP Test Plan
- Deploy an IDP in an Operational Federation
| Main Page | Next |
|---|
