Example: Set up the PingDataGovernance Policy Administration GUI in OIDC mode (PingFederate) - PingDataGovernance

Example: Set up the PingDataGovernance Policy Administration GUI in OIDC mode (PingFederate) - PingDataGovernance - 8.2

PingDataGovernance

bundle

pingdatagovernance-82

ft:publication_title

PingDataGovernance

Product_Version_ce

PingDataGovernance 8.2

category

Product

pdg-82

pingdatagovernance

ContentType_ce

Page created: 22 Jul 2020 |

Page updated: 9 Feb 2021

| 1 min read

8.2 PingDataGovernance Product Installation User task Product documentation Content Type Data Governance Capability

Use this example as a reference to set up the PingDataGovernance Policy Administration GUI to handle sign-ons using a PingFederate OpenID Connect (OIDC) provider.

$ bin/setup oidc \
  --oidcHostname <ping-federate-hostname> \
  --oidcPort <ping-federate-port> \
  --clientId pingdatagovernance-pap \
  --generateSelfSignedCertificate \
  --decisionPointSharedSecret datagovernance \
  --hostname <pap-hostname> \
  --port <pap-port> \
  --adminPort <admin-port> \
  --licenseKeyFile <path-to-license>

The Policy Administration GUI uses the provided OIDC host name and OIDC to query the PingFederate server’s autodiscovery endpoint for the information it needs to make OIDC requests. The provided client ID represents the Policy Administration GUI and must be configured in PingFederate. For more information about configuring PingFederate, see Configuring an Authentication Server for OpenID Connect single sign-on.