Difference between revisions of "PingFederate Implementation"
Matt.Moyer (Talk | contribs) |
|||
| Line 10: | Line 10: | ||
* [[How to Implement a GFIPM Identity Provider Software Instance]] | * [[How to Implement a GFIPM Identity Provider Software Instance]] | ||
| − | * [[Implement a GFIPM | + | * [[How to Implement a GFIPM Service Provider]] |
Latest revision as of 21:26, 15 June 2013
| Main Page |
|---|
GTRI does not have any direct experience with implementing PingFederate. However, one NIEF member is currently using PingFederate, and GTRI has provided some assistance during the implementation process. During our limited experience, we found only one known issue. Specifically, PingFederate is not able to parse a GFIPM Trust Fabric file, which includes entries for multiple entities (IDPs and SPs). PingFederate requires that each entity in the federation be defined individually. You should be able to extract individual entities out of the GFIPM Trust Fabric file and load them into PingFederate according to the PingFederate documentation.
For high-level, broadly detailed information about configuring an IDP or an SP software instance, see the following articles:
- How to Implement a GFIPM Identity Provider Software Instance
- How to Implement a GFIPM Service Provider
| Main Page |
|---|
