Skip to content
Start with Identity
Protocol

OAuth 2.0 Authorization Server Metadata

OAuth 2.0 Authorization Server Metadata (RFC 8414, Proposed Standard, June 2018) is a JSON document an authorization server publishes at /.well-known/oauth-authorization-server listing its issuer, endpoints, signing keys location, and supported grant types, scopes, and features, so clients can configure themselves automatically.

It generalizes OpenID Connect Discovery (/.well-known/openid-configuration) to plain OAuth, and the two documents share most field names. Metadata is how a client learns whether a server supports PKCE, PAR, DPoP, or Client ID Metadata Documents without guessing, and it is the second hop of discovery after a resource points to its authorization server through RFC 9728. The security rule that matters is the issuer check: the value in the document must exactly match the issuer the client expected, and with RFC 9207 the iss returned in authorization responses must match too, which is the defense against mix-up attacks when a client talks to more than one authorization server.

See also: protected resource metadata, authorization server, JWKS, OIDC, MCP authorization, OpenID Connect

Last reviewed By SWI Community TeamSuggest a correctionHow we research