Skip to main content
GET
Discover the public OAuth endpoints and authorization-code, PKCE, refresh, and revocation mechanisms supported by this environment.

Authentication

None.

Request examples

Follow the documented encoding and authentication for this route. The action API’s envelope and idempotency rules apply only to action invocations.

Response

OAuth authorization-server metadata with absolute endpoint URLs on the canonical issuer origin.
HTTP 200

Operation notes

  • Only the code response type and query response mode are advertised.
  • Clients can use dynamic registration or a Client ID Metadata Document (CIMD). client_id_metadata_document_supported is true; a CIMD client uses its public HTTPS document URL as client_id.
  • A CIMD JSON document must contain an exact matching client_id, a nonempty client_name of at most 120 characters, and 1–10 exact redirect_uris. Use public-client authentication none with S256 PKCE; authorization_code is required and refresh_token is optional.
  • Serve CIMD as uncompressed JSON over public HTTPS on port 443, with an explicit path, without credentials, fragments, dot segments, or redirects. The document must be at most 64 KiB and respond within 5 seconds. Cached metadata expires within 5 minutes; token exchange and refresh use the metadata bound to the grant.
  • When OpenID Connect is available, authorization-server metadata also advertises openid and email scopes, userinfo_endpoint, and jwks_uri. Otherwise these scopes and endpoints are absent from that metadata.
  • Token and revocation authentication methods are none. Public clients use client_id and S256 PKCE instead of a client secret.
  • offline_access is a renewal-related scope marker, not a product permission. Issuing a refresh token depends on whether refresh_token was registered as a grant type.
  • Check the returned iss value on the final client callback against issuer. Both successful and denied authorization callbacks include iss, and echo state when one was supplied.

Errors