Difference between revisions of "How to Implement a GFIPM Identity Provider"
From GFIPM Implementation Wiki
Line 8: | Line 8: | ||
A [http://gfipm.net/ 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 [[How to Implement a Service Provider | GFIPM Service Provider]]. This article lists the steps necessary to implement an IDP: | A [http://gfipm.net/ 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 [[How to Implement a Service Provider | GFIPM Service Provider]]. This article lists the steps necessary to implement an IDP: | ||
− | # [[Develop a GFIPM Information Sharing Plan for an | + | # [[Develop a GFIPM Information Sharing Plan for an Identity Provider]] |
# [[Submit a Request for Federation Membership as an Identity Provider]] | # [[Submit a Request for Federation Membership as an Identity Provider]] | ||
# [[Choose an IDP Product]] | # [[Choose an IDP Product]] |
Revision as of 15:03, 22 May 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:
- 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 |