/oauth2/.well-known/openid-configuration

Lets relying parties retrieve the OpenID Provider configuration by HTTP GET as specified by OpenID Connect Discovery 1.0.

When the OpenID Connect provider is configured in a subrealm, relying parties can get the configuration by passing in the full path to the realm in the URL. For example, if the OpenID Connect provider is configured in a subrealm named subrealm1, which is a child of the Top Level Realm, the URL would resemble the following: https://openam.example.com:8443/openam/oauth2/realms/root/realms/subrealm1/.well-known/openid-configuration.

After the relying party has discovered who the provider for the end user is, they can discover the provider's configuration:

$ curl "https://openam.example.com:8443/openam/oauth2/.well-known/openid-configuration"
{
   "request_parameter_supported":true,
   "claims_parameter_supported":false,
   "introspection_endpoint":"https://openam.example.com:8443/openam/oauth2/introspect",
   "check_session_iframe":"https://openam.example.com:8443/openam/oauth2/connect/checkSession",
   "scopes_supported":[
      "address",
      "phone",
      "openid",
      "profile",
      "email"
   ],
   "userinfo_endpoint":"https://openam.example.com:8443/openam/oauth2/userinfo",
   "jwks_uri":"https://openam.example.com:8443/openam/oauth2/connect/jwk_uri",
   "registration_endpoint":"https://openam.example.com:8443/openam/oauth2/register",
  ....
}