The Microsoft Azure® identity bridge uses OpenID Connect and OAuth to connect to your Azure 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 Azure provider.
To configure the identity bridge, you'll be working on both the Azure and PingOne sides and copying information from your Azure tenant to the PingOne identity bridge setup.
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.