Configuring PingFederate as a PingAccess token provider - PingCentral

Configuring PingFederate as a PingAccess token provider - PingCentral - 1.6

PingCentral

bundle

pingcentral-16

ft:publication_title

PingCentral

Product_Version_ce

PingCentral 1.6

category

Administrator

Audience

Developer

Product

pc-16

pingcentral

ContentType_ce

Page created: 11 Nov 2020 |

Page updated: 22 Feb 2021

| 1 min read

Product PingCentral 16 Developer Audience Administrator 1.6

To add PingAccess environments to PingCentral, PingFederate must be configured as the token provider. If you have PingFederate and PingAccess environments established, this configuration is likely in place. So if you set up a new environment or change the token provider settings, be aware of this requirement and ensure PingFederate and PingAccess are configured correctly.

To configure PingFederate as the token provider for PingAccess, the Issuer URL in PingAccess must either match the Base URL in PingFederate, or one of the virtual hosts defined in PingFederate.

To configure PingFederate as a PingAccess token provider, ensure the PingAccess Issuer URL and the PingFederate Base URL match.
If a virtual host is defined in PingFederate, continue to step 3.
To locate this information:
- In PingFederate, to locate the Base URL field, go to System > Protocol Settings > Federation Info, as shown in the following example.
- In PingAccess, to locate the Issuer URLfield, go to System > Token Provider.
  Note: In some versions of PingAccess, the Issuer URL might exist as separate Host and Port fields.
If a virtual host is defined in PingFederate, the PingAccess Issuer URL can reference that instead of Base URL. In PingFederate, to locate the virtual host, go the System > Virtual Host Names page and review the information in the Host Domain Name field.