Difference between revisions of "How to Implement a GFIPM Identity Provider"
From GFIPM Implementation Wiki
Matt.Moyer (Talk | contribs) |
Matt.Moyer (Talk | contribs) |
||
| Line 8: | Line 8: | ||
# [[How to Develop a GFIPM Information Sharing Plan for an Identity Provider]] | # [[How to Develop a GFIPM Information Sharing Plan for an Identity Provider]] | ||
| − | # [[How to Submit a Request for Federation Membership as | + | # [[How to Submit a Request for Federation Membership as a GFIPM Identity Provider]] |
# [[How to Choose an Identity Provider Product]] | # [[How to Choose an Identity Provider Product]] | ||
# [[How to Implement a GFIPM Identity Provider Software Instance]] | # [[How to Implement a GFIPM Identity Provider Software Instance]] | ||
Revision as of 20:32, 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
- How to Submit a Request for Federation Membership as a GFIPM Identity Provider
- How to Choose an 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
| Main Page | Next |
|---|
