Difference between revisions of "How to Implement a GFIPM Identity Provider"

From GFIPM Implementation Wiki
Jump to: navigation, search
Line 4: Line 4:
  
  
A [http://gfipm.net/ GFIPM] 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:
+
A [http://gfipm.net/ GFIPM] 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 IDP]]
 
# [[Develop a GFIPM Information Sharing Plan for an IDP]]

Revision as of 17:12, 16 May 2011

Main Page


A GFIPM 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:

  1. Develop a GFIPM Information Sharing Plan for an IDP
  2. Submit a Request for Federation Membership
  3. Choose an IDP Product
  4. Implement a GFIPM IDP
  5. Write an IDP Test Plan
  6. Deploy an IDP in a Test Environment
  7. Execute an IDP Test Plan
  8. Deploy an IDP in an Operational Federation