Skip to content

OpenID Connect Discovery 1.0

Spec: openid.net/specs/openid-connect-discovery-1_0.htmlStatus: Full

OpenID Connect Discovery lets clients dynamically learn an OP's endpoints and capabilities via a well-known URL.

Implemented

  • Discovery endpointGET /.well-known/openid-configuration.
  • JWKS endpoint advertisementjwks_uri points to /.well-known/jwks.json.
  • Core endpointsissuer, authorization_endpoint, token_endpoint, userinfo_endpoint, end_session_endpoint are always advertised.
  • Conditional endpointsregistration_endpoint is included in the discovery metadata only when the Dynamic Client Registration feature is enabled for the tenant.
  • Supported response typescode, token, id_token, code token, code id_token, token id_token, code token id_token.
  • Supported response modesquery, fragment, form_post.
  • Supported grant typesauthorization_code, client_credentials, refresh_token, plus Auth0-compatible passwordless OTP grant.
  • Supported scopesopenid, profile, email, address, phone, offline_access.
  • Supported subject typespublic.
  • Supported signing algorithmsRS256 (ID tokens), plus additional algorithms for access tokens.
  • Supported token endpoint auth methodsclient_secret_basic, client_secret_post, none.
  • Supported claims — published in claims_supported.

Declared but not yet implemented

Some endpoints are advertised for compatibility but the underlying functionality is on the roadmap:

  • revocation_endpoint — RFC 7009 token revocation.
  • device_authorization_endpoint — RFC 8628 device flow.

See the Standards overview for details.

Released under the MIT License.