IETF OAuth · Discovery

OAuth Client ID Metadata Document

Lets a client use an HTTPS URL as its client_id; the authorization server fetches the metadata document at that URL instead of requiring prior or dynamic registration.

Working group draftWorking group document, intended Standards TrackCanonical documentcimd

Revisions

draft-022026-07-06current
draft-002025-10-08superseded
Adopted by the OAuth working group; replaces the individual draft.
draft-parecki-032025-07-22superseded
draft-parecki-002024-07-02superseded

Relations 4

OAuth Client ID Metadata Document builds on 1

The OAuth 2.0 Authorization FrameworkpublishedDefines a client_id syntax and the authorization server behaviour for it.Source

OAuth Client ID Metadata Document references 1

OAuth 2.0 Dynamic Client Registration ProtocolpublishedThe metadata document reuses the client metadata fields of dynamic registration.Source

OAuth Client ID Metadata Document solves the same problem as 1

OAuth 2.0 Dynamic Client Registration ProtocolpublishedBoth let a client the authorization server has never seen become usable: dynamic registration by an API call that creates a record, the metadata document by a URL the server fetches on demand. The MCP Authorization specification moved its default from the first to the second in revision 2026-07-28. Source

OAuth Client ID Metadata Document is referenced by 1

MCP AuthorizationpublishedClient ID Metadata Documents are the recommended registration method.Source

Defines in the shared model

No features of this document are recorded yet. Features are what the atlases observe and the explorer cites; they are added as the products need them.