Skip to main content
VerifiedStandard or protocol

RFC 7591, OAuth 2.0 dynamic client registration

Published in July 2015, this lets a client register itself with an authorization server and receive credentials without a human filling in a form. It is how agent tooling connects to servers nobody pre arranged, and it is also the mechanism the confused deputy attack abuses. The July 2026 MCP revision deprecates it.

The verdict

Verified

The document exists. The ledger fetched it at its publisher and quotes it.

Key facts

What the sources say

Record ID
AAL-2026-0011
Kind
Standard or protocol
Jurisdiction
Global
Last verified
Added
  • The specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers.
  • MCP originally recommended it so clients could connect to servers they did not know in advance.
  • The MCP security guidance shows an attacker registering a client with an attacker controlled redirect URI to harvest an authorization code.
  • The MCP specification of 28 July 2026 marks dynamic client registration deprecated and retained only for backwards compatibility.

Dimension by dimension

2 dimensions, each one stated, silent or open

Identity, Human approval. Stated means the document you can open below says it; silent means the ledger read the document and it does not.

IdentityStated
A client identity can be created on demand, which means an identifier alone proves nothing about who is behind it.RFC Editor, RFC 7591, primary source, 1 July 2015.
Human approvalSilent
The specification does not require a person to approve a new registration, which is why proxies must add their own consent step.RFC Editor, RFC 7591, primary source, 1 July 2015.

What it changes

For a team deploying an agent

If your authorization server accepts dynamic registration, anyone can mint a client. Pair it with per client consent and exact redirect URI matching, or move to client identity documents as MCP now advises. Treat a self registered client id as an unverified claim, not an identity.

Sources

What this record was verified against

  1. RFC Editor, RFC 7591Primary · 1 July 2015
  2. Model Context Protocol specification 2026-07-28, AuthorizationPrimary · 28 July 2026

Related

Records that sit beside this one

Cite this record

Free to reuse under CC BY 4.0, with attribution. The record ID AAL-2026-0011 is permanent and is never reused.

In a sentence
According to the GAGE Agent Authority Ledger (as of 15 September 2026), rfc 7591, oauth 2.0 dynamic client registration.
APA
GAGE (Global Academy of Generative-AI Education). (2026). RFC 7591, OAuth 2.0 dynamic client registration. Agent Authority Ledger. Retrieved 15 September 2026, from https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0011-rfc-7591-oauth-2-0-dynamic-client-registration
MLA
"RFC 7591, OAuth 2.0 dynamic client registration." Agent Authority Ledger, GAGE (Global Academy of Generative-AI Education), 15 September 2026, https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0011-rfc-7591-oauth-2-0-dynamic-client-registration.
Chicago
GAGE (Global Academy of Generative-AI Education). "RFC 7591, OAuth 2.0 dynamic client registration." Agent Authority Ledger. Last modified 15 September 2026. https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0011-rfc-7591-oauth-2-0-dynamic-client-registration.
Permalink
https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0011-rfc-7591-oauth-2-0-dynamic-client-registration

Last updated . Every record re verified . The ledger is checked weekly, every Monday, and the same day for any NIST, IETF or MCP publication.

Back to the full ledger, or every record for Global and every standard or protocol record.

GAGE briefings tell you which AI regulation deadlines are coming, what they actually require of you, and when a program opens.

Powered by GAGE, free EU AI Act tools from the Global Academy of Generative-AI Education
CallEmailHelp