IETF OAuth · Protocol
OAuth 2.0 Dynamic Client Registration Protocol
Lets a client register itself with an authorization server at run time through an HTTP API and receive a client identifier, instead of being registered by hand.
PublishedProposed StandardCanonical documentrfc7591
Revisions
- rfccurrent
Relations 5
OAuth 2.0 Dynamic Client Registration Protocol builds on 1
- The OAuth 2.0 Authorization FrameworkpublishedRegisters OAuth clients; the client metadata it defines is reused by later documents.Source
OAuth 2.0 Dynamic Client Registration Protocol solves the same problem as 2
- OAuth Client ID Metadata DocumentWG draftBoth 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
- auth.mdpublishedBoth answer how a client nobody registered gets credentials. Dynamic registration is a generic API; auth.md is a human- and agent-readable file plus metadata aimed at agents signing up for a service on a user's behalf.
OAuth 2.0 Dynamic Client Registration Protocol is referenced by 2
- OAuth Client ID Metadata DocumentWG draftThe metadata document reuses the client metadata fields of dynamic registration.Source
- MCP AuthorizationpublishedDynamic Client Registration remains an option, deprecated in revision 2026-07-28.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.