An OAuth client that supports more than one authorization server has a routing problem that ordinary state validation does not solve. A malicious authorization server can return an authorization response that the client mistakes for one from a trusted server. RFC 9207 addresses this class of mix-up attacks by adding an iss parameter to the authorization response. The value identifies the authorization server that created the response, including error responses. The client then compares it with the issuer value it trusts for that authorization transaction.
The check is small, but its placement matters. It belongs before the client exchanges an authorization code. The callback handler should already know which issuer it selected for the transaction from server-side state or another protected correlation record. It should not infer the expected issuer from the callback parameters, because the attacker controls those parameters along with the response.
RFC 9207 says an authorization server that supports the specification must include iss in authorization responses. Clients interacting with an authorization server that publishes OAuth metadata must compare the response value with the metadata issuer. The RFC defines the value as the issuer identifier from the server metadata, not a display name, hostname fragment, or tenant label invented by the client. Clients should use an exact comparison and maintain one canonical representation of each issuer.
RFC 9700 places this mechanism among the recommended defenses against authorization server mix-up. The larger defense still depends on transaction binding. The client needs to remember the selected authorization server, redirect URI, PKCE verifier, state value, and other transaction-specific data in a protected location. The iss parameter makes the server's identity explicit, but it does not repair a transaction that was already confused before the callback arrived.
What to validate
The authorization server metadata should advertise authorization_response_iss_parameter_supported when the server supports RFC 9207. A client integration should reject a response whose iss is missing when that protection is required by policy, or whose value does not exactly match the issuer selected for the transaction.
Error responses need the same treatment. A login failure, consent denial, or temporary server error can still move a client into a branch that logs, retries, or exchanges a code. If a client only checks iss on successful callbacks, a mixed-up error path can still produce the wrong behavior.
The expected issuer should come from a configured trust entry, not from the query string. For a multi-tenant service, the entry should identify the exact tenant or realm if those values produce separate issuer identifiers. A trailing slash, case difference, or different URL form can make string comparison fail. Choose one canonical issuer value in configuration and compare that value consistently.
OIDC clients also need to validate the ID token issuer. An iss parameter in the authorization response and an iss claim in a token answer related but separate questions. The response parameter identifies the server that created the response. The token issuer claim is evaluated as part of token validation. One check does not replace the other.
A practical rollout
Start with metadata discovery. Record which authorization servers advertise RFC 9207 support and which clients can enforce it. Add a negative test that sends a response with a missing or wrong iss and confirms that no token exchange occurs. Add a successful test for each configured issuer, including issuers that use different tenant identifiers.
Legacy servers that do not support the parameter need an explicit migration decision. A client can keep a narrowly scoped compatibility path while the server is upgraded, but that path should be visible in configuration and retired. Silently accepting a missing issuer prevents the organization from knowing which integrations are protected.
Log the expected issuer, the received issuer when present, the authorization server configuration entry, and the transaction identifier. Do not log authorization codes, PKCE verifiers, access tokens, or other credentials. A mismatch should produce a security event and stop the flow, not a retry against another issuer.
The iss response parameter is useful because it closes a routing ambiguity at the point where the response enters the client. It remains one part of a chain that includes exact redirect URI matching, PKCE, state validation, token audience checks, and a clear trust configuration.