The OpenID Connect identity bridge uses OpenID Connect and OAuth to connect to your OpenID Connect provider (OP) to authenticate your users and access user information. In OpenID terms, PingOne is the Relying Party (RP) that sends authentication and information requests to the OpenID Connect provider.
You will need to supply the OAuth Client ID and Client Secret values registered for your OpenID Connect provider.
OpenID Connect supports a discovery mechanism whereby an OpenID Connect host
publishes metadata using a well-known URL, by convention of the form:
https://host.com/.well-known/openid-configuration
. The URL
returns OpenID Connect and OAuth endpoints, supported scopes and claims, public keys
used to sign tokens, and other metadata. We use this metadata to complete your
authentication requests and requests for user information.
If your OpenID Connect provider doesn't have a discovery endpoint (URL) that we can use to query your IdP for the metadata, we will display the information we need and you will supply these values. See the configuration or documentation for your OpenID Connect provider to find the necessary values.