Skip to content
IAM Insights

Explainers · Glossary

OAuth 2.0 Authorization Server Issuer Identification

Issuer Identification · iss parameter · RFC 9207 · RFC9207

An OAuth mechanism (RFC 9207) in which the authorization server adds its identity (iss) to each authorization response, so the client can check it came from the server it started with, to counter mix-up attacks.

reference →

In our briefings

The claim each of the newest briefings on OAuth 2.0 Authorization Server Issuer Identification would have you leave with.

  1. None of the authorization changes in MCP's 2026-07-28 revision is listed under Major changes; they sit under Minor changes and Deprecated. SEP-2352 says clients 'MUST key persisted credentials by the issuer identifier, MUST NOT reuse them with a different authorization server, and MUST re-register when the authorization server changes'. Authorization servers should include the RFC 9207 iss (issuer) parameter in authorization responses, and clients must check a present iss against the recorded issuer before redeeming the authorization code (SEP-2468). SEP-837 requires clients to specify an appropriate application_type during Dynamic Client Registration, to avoid OpenID Connect redirect URI conflicts. Dynamic Client Registration itself is deprecated 'as a client registration mechanism in favor of Client ID Metadata Documents' (PR #2858) and remains available for authorization servers that do not support them. The same revision adopts a lifecycle policy with 'a minimum twelve-month deprecation window'; the changelog gives no removal date for Dynamic Client Registration and does not say when its window starts.

    MCP's July spec ties client credentials to the authorization server that issued themBI-FIND-2026-0395

  2. Under this draft a client's identity is a web address and whatever its owner publishes there. The client_id is an https URL, which revision -03 says "MUST contain a path component other than /", and the JSON document at that URL "MUST contain a client_id property whose value MUST match" it. The authorization server learns the client's name, redirect addresses and keys by fetching that document. Its security section says a client that changes its URL is "a brand new client with no relationship to the previous one", and that losing control of the domain would let a third party "assume the client's identity". We read this as a name anyone can look up. That is more than an anonymous registration gives a server, though it says nothing about what software sits behind the name.

    OAuth's URL client ID draft tightens server rules in -03; the client is still whoever controls the URLBI-FIND-2026-0319

  3. Paktiti's argument is that RFC 9207 fixes the mix-up attack inside the authorization response, which token exchange (RFC 8693) does not have, and she says the JWT bearer grant (RFC 7523) and the SAML 2.0 bearer grant (RFC 7522) share that shape. In those grants the token endpoint itself has to tie each signing key to its issuer and match sub only against accounts under the issuer it confirmed. Her case is n8n's CVE-2026-59208, which she describes as a flat pool of trusted keys: the signature matched a trusted key, and nothing confirmed that the key belonged to the issuer the sub claim was supposed to come from. n8n's own advisory, GHSA-mq3m-f8x3-579w, puts the flaw in the account lookup instead, and our account follows the advisory: with more than one trusted token-exchange issuer configured, n8n matched external identities to local accounts by the JWT sub claim alone and ignored iss, so a valid token from one issuer could sign in as a user with the same sub under another. Only instances with token exchange turned on and more than one trusted issuer were exposed; versions 2.27.4 and 2.28.1 fix it, and until an upgrade the advisory suggests dropping to one trusted issuer or turning token exchange off. The rule was already written down: our briefing on RFC 8725 found the JWT best-practice RFC requires that a JWT's keys belong to its issuer.

    RFC 9207's issuer check stops at the redirect, and n8n's token-exchange flaw sat just past itBI-FIND-2026-1887

›Cited in 17 briefings

Every briefing that discusses this term, newest first.

  1. MCP's July spec ties client credentials to the authorization server that issued them

    Article · · Model Context Protocol project · Jul 28, 2026

  2. OAuth's URL client ID draft tightens server rules in -03; the client is still whoever controls the URL

    Draft · · IETF Datatracker · Aaron Parecki et al. · Jul 6, 2026

  3. RFC 9207's issuer check stops at the redirect, and n8n's token-exchange flaw sat just past it

    Article · · WorkOS · Maria Paktiti · Jul 20, 2026

  4. TPX replaces an app's embedded AI provider key with a capped, metered grant the user approves at their provider

    Article · · tokenpony.dev · Alex Polvi · Jul 20, 2026

  5. DIF's agent spec names every AI agent by a DID; the IETF's Agent Name Service switched to domain names

    Article · · Decentralized Identity Foundation (KYA-OS) · Dylan Hobbs et al. · Jul 29, 2026

  6. Three MCP auth flaws in a month, and the spec had already written the rule the SDKs skipped

    Article · · WorkOS Blog · Maria Paktiti · Oct 2, 2026

  7. MCP's authorization spec makes the agent a plain OAuth client and leaves delegation to an extension

    Article · · Model Context Protocol project · Jul 28, 2026

  8. OAuth 2.1's October draft bans plain PKCE and adds browser-app rules; 2.1-only clients can fail on older servers

    Draft · · IETF Datatracker · Dick Hardt et al. · Mar 2, 2026

  9. An OAuth client brokering many tools, as agent services do, can let a rogue tool take over a user's other tools

    Draft · · IETF Datatracker · Tim Würtele et al. · Mar 2, 2026

  10. Credential wallet draft makes holder binding a MUST; its own SD-JWT profile names no way to provide it

    Draft · · IETF Datatracker · Leif Johansson et al. · Nov 4, 2025

  11. A rogue OAuth server can collect a client's signed assertion and replay it at an honest server the client also uses

    Article · · IACR Cryptology ePrint Archive · Pedram Hosseyni et al. · Apr 7, 2025

  12. FAPI 2.0 issues only sender-constrained access tokens and leaves public clients out

    Article · · OpenID Foundation · Daniel Fett et al. · Feb 22, 2025

  13. RFC 9700 bans OAuth's password grant and loose redirect matching; binding access tokens stays a SHOULD

    Article · · IETF (RFC Editor) · Torsten Lodderstedt et al. · Jan 2025

  14. In May 2023, Parecki described OAuth 2.1 as consolidation and DPoP as token protection

    Video · · Identiverse - A CRA Resource · Jun 17, 2024

  15. RFC 9207 has OAuth servers name themselves in each response; clients must refuse a missing name only where they expect one

    Article · · RFC Editor · Karsten Meyer zu Selhausen et al. · Mar 1, 2022

  16. Trying to prove OAuth 2.0 secure, a 2016 Trier paper found four attacks, the IdP mix-up among them

    Paper · · arXiv · Daniel Fett et al. · Jan 6, 2016

  17. In 2015, OpenID Connect discovery let an attacker's server choose where a client sent the user's code

    Paper · · arXiv · Christian Mainka et al. · Aug 18, 2015

Related terms

What appears alongside OAuth 2.0 Authorization Server Issuer Identification in the same briefings.

Mix-up attackUpdates to OAuth JWT Client Authentication and Assertion-Based GrantsPushed Authorization RequestsOAuth 2.0 Security Best Current PracticeOAuth 2.0 for Native Apps (RFC 8252)JWT-Secured Authorization Request (JAR, RFC 9101)Model Context Protocol projectUpdates to OAuth 2.0 Security Best Current Practice