When you create a PingCentral template based on an existing PingFederate application, or add an existing PingFederate application to PingCentral, the raw JSON is saved to PingCentral.
PingCentral does not display the entire JSON file when you select an application, but the most relevant information is provided to help you distinguish between applications.
For OAuth or OIDC, the following items are saved:
- The client application.
- The ATM, if one exists.
- The parent ATM, if one exists.
- The OIDC policy, if one exists.
- Definitions of exclusive scopes referenced by the client.
Refer to OIDC connection orchestration to see a diagram of the PingFederate items orchestrated by PingCentral.
For SAML SP connections, the following items are saved:
- Connection information.
- Attribute names defined in the associated authentication policy contract.
Refer to SAML connection orchestration to see a diagram of the PingFederate items orchestrated by PingCentral.
Refer to the following for instructions on creating and updating OAuth and SAML SP templates: