How to Implement a NIEF Identity Provider: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
(One intermediate revision by the same user not shown) | |||
Line 9: | Line 9: | ||
# [[How to Develop a NIEF Information Sharing Plan for an Identity Provider]] | # [[How to Develop a NIEF Information Sharing Plan for an Identity Provider]] | ||
# [[How to Choose a NIEF Identity Provider Product]] | # [[How to Choose a NIEF Identity Provider Product]] | ||
# [[Interoperability Testing with NIEF Testbed]] | |||
{| | {| | ||
!class="gfipmnav"|[[ | !class="gfipmnav"|[[NIEF Implementers Wiki|Main Page]] | ||
!class="gfipmnav"|[[How to Develop a | !class="gfipmnav"|[[How to Develop a NIEF Information Sharing Plan for an Identity Provider|Next]] | ||
|} | |} |
Latest revision as of 19:16, 23 January 2019
Main Page | Next |
---|
A NIEF Identity Provider (IDP) collects information (typically from an existing identity store) about a local user and generates a SAML assertion about that user for the benefit of engaging in single sign on (SSO) with a NIEF Service Provider. The following steps are required to implement a NIEF IDP. For each step, there is an article describing how to do it.
- How to Develop a NIEF Information Sharing Plan for an Identity Provider
- How to Choose a NIEF Identity Provider Product
- Interoperability Testing with NIEF Testbed
Main Page | Next |
---|