OPTIONAL. JSON array containing a list of the Authentication Context Class References that this OP supports.
REQUIRED. URL of the OP's OAuth 2.0 Authorization Endpoint
[OpenID.Core].
This URL MUST use the https scheme and MAY contain port, path, and query parameter components.
OPTIONAL. Boolean value specifying whether the OP can pass a sid (session ID) Claim in the Logout Token to identify the
RP session with the OP. If supported, the sid Claim is also included in ID Tokens issued by the OP. If omitted, the default
value is false.
OPTIONAL. Boolean value specifying whether the OP supports back-channel logout, with true indicating support. If omitted,
the default value is false.
REQUIRED. URL of an OP iframe that supports cross-origin communications for session state information with the
RP Client, using the HTML5 postMessage API. This URL MUST use the https scheme and MAY contain port, path, and
query parameter components. The page is loaded from an invisible iframe embedded in an RP page so that it can run
in the OP's security context. It accepts postMessage requests from the relevant RP iframe and uses postMessage to
post back the login status of the End-User at the OP.
OPTIONAL. JSON array containing a list of the Claim Types that the OpenID Provider supports. These Claim Types are described
in Section 5.6 of
OpenID Connect Core 1.0
[OpenID.Core]. Values defined by this specification are normal, aggregated, and distributed. If omitted, the
implementation supports only normal Claims.
OPTIONAL. Boolean value specifying whether the OP supports use of the claims parameter, with true indicating support. If
omitted, the default value is false.
RECOMMENDED. JSON array containing a list of the Claim Names of the Claims that the OpenID Provider MAY be able to supply values for. Note that for privacy or other reasons, this might not be an exhaustive list.
OPTIONAL. JSON array containing a list of Proof Key for Code Exchange (PKCE) [RFC7636] code challenge methods supported by this authorization server. Code challenge method values are used in the "code_challenge_method" parameter defined in Section 4.3 of [RFC7636]. The valid code challenge method values are those registered in the IANA "PKCE Code Challenge Methods" registry [IANA.OAuth.Parameters]. If omitted, the authorization server does not support PKCE.
OPTIONAL. JSON array containing a list of the display parameter values that the OpenID Provider supports. These values are
described in Section 3.1.2.1 of
OpenID Connect Core 1.0
[OpenID.Core].
REQUIRED. URL at the OP to which an RP can perform a redirect to request that the End-User be logged out at the OP.
OPTIONAL. Boolean value specifying whether the OP can pass iss (issuer) and sid (session ID) query parameters to identify
the RP session with the OP when the frontchannel_logout_uri is used. If supported, the sid Claim is also included in
ID Tokens issued by the OP. If omitted, the default value is false.
OPTIONAL. Boolean value specifying whether the OP supports HTTP-based logout, with true indicating support. If omitted,
the default value is false.
OPTIONAL. JSON array containing a list of the OAuth 2.0 Grant Type values that this OP supports. Dynamic OpenID Providers
MUST support the authorization_code and implicit Grant Type values and MAY support other Grant Types. If omitted, the
default value is ["authorization_code", "implicit"].
The fully qualified URL of the server's introspection endpoint defined by OAuth Token Introspection [RFC7662].
REQUIRED. URL using the https scheme with no query or fragment component that the OP asserts as its Issuer
Identifier. If Issuer discovery is supported
(see Section 2),
this value MUST be identical to the issuer value
returned by WebFinger. This also MUST be identical to the iss Claim value in ID Tokens issued from this Issuer.
REQUIRED. URL of the OP's JWK Set
[JWK]
document, which MUST use the https scheme. This contains the signing key(s) the RP uses to validate signatures from
the OP. The JWK Set MAY also contain the Server's encryption key(s), which are used by RPs to encrypt requests to the Server.
When both signing and encryption keys are made available, a use (public key use) parameter value is REQUIRED for all keys
in the referenced JWK Set to indicate each key's intended usage. Although some algorithms allow the same key to be used for
both signatures and encryption, doing so is NOT RECOMMENDED, as it is less secure. The JWK x5c parameter MAY be used to provide
X.509 representations of keys provided. When used, the bare key values MUST still be present and MUST match those in the
certificate. The JWK Set MUST NOT contain private or symmetric key values.
RECOMMENDED. URL of the OP's Dynamic Client Registration Endpoint
[OpenID.Registration],
which MUST use the https scheme.
OPTIONAL. JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for Request Objects,
which are described in Section 6.1 of
OpenID Connect Core 1.0
[OpenID.Core]. These algorithms are used both when the Request Object is passed by value (using the request parameter) and
when it is passed by reference (using the request_uri parameter). Servers SHOULD support none and RS256.
OPTIONAL. JSON array containing a list of the OAuth 2.0 response_mode values that this OP supports, as specified in
OAuth 2.0 Multiple Response Type Encoding Practices
[OAuth.Responses]. If omitted, the default for Dynamic OpenID Providers is ["query", "fragment"].
REQUIRED. JSON array containing a list of the OAuth 2.0 response_type values that this OP supports. Dynamic OpenID
Providers MUST support the code, id_token, and the id_token token Response Type values.
The fully qualified URL of the server's revocation endpoint defined by OAuth 2.0 Token Revocation [RFC7009].
RECOMMENDED. JSON array containing a list of the OAuth 2.0 [RFC6749] scope values that this server supports. The server MUST support the openid scope value. Servers MAY choose not to advertise some supported scope values even when this parameter is used, although those defined in [OpenID.Core] SHOULD be listed, if supported.
OPTIONAL. URL of a page containing human-readable information that developers might want or need to know when using the OpenID Provider. In particular, if the OpenID Provider does not support Dynamic Client Registration, then information on how to register Clients needs to be provided in this documentation.
REQUIRED. JSON array containing a list of the Subject Identifier types that this OP supports. Valid types include pairwise
and public.
URL of the OP's OAuth 2.0 Token Endpoint
[OpenID.Core].
This is REQUIRED unless only the Implicit Flow is used. This URL MUST use the https scheme and MAY contain
port, path, and query parameter components.
OPTIONAL. JSON array containing a list of Client Authentication methods supported by this Token Endpoint.
The options are client_secret_post, client_secret_basic, client_secret_jwt, and private_key_jwt, as
described in Section 9 of
OpenID Connect Core 1.0
[OpenID.Core]. Other authentication methods MAY be defined by extensions. If omitted, the default is
client_secret_basic -- the HTTP Basic Authentication Scheme specified in Section 2.3.1 of
OAuth 2.0 [RFC6749].
OPTIONAL. JSON array containing a list of the JWS signing algorithms (alg values) supported by the
Token Endpoint for the signature on the JWT
[JWT]
used to authenticate the Client at the Token Endpoint for the private_key_jwt and client_secret_jwt
authentication methods. Servers SHOULD support RS256. The value none MUST NOT be used.
OPTIONAL. Languages and scripts supported for the user interface, represented as a JSON array of BCP47 [RFC5646] language tag values.
RECOMMENDED. URL of the OP's UserInfo Endpoint [OpenID.Core]. This URL MUST use the https scheme and MAY contain port, path, and query parameter components.
OpenID Providers have metadata describing their configuration.