[Client][Auth] SEP-2468: Validate iss parameter in authorization response (RFC 9207)

Implements SEP-2468 for the MCP Spec 2026-07-28 release.

Tracked by umbrella #338.

Spec summary

Requires MCP authorization responses to include an explicit iss (issuer) parameter per RFC 9207. Clients MUST validate iss against the AS that initiated the flow to mitigate authorization mix-up attacks in multi-IdP environments.

PHP SDK changes

• When handling the authorization-code redirect, the client must validate the returned iss matches the AS that produced the authorization_endpoint URL.
• Required for any multi-AS scenario; cross-cuts with #319 (Auth Code + PKCE) but filed separately because the validation logic crosses callback + AS-metadata state.
• Server-side: N/A — MCP servers are resource servers, not authorization servers; iss is emitted by the AS.

Related

• Umbrella #338
• Sub-task / depends on: #319 (Auth Code + PKCE foundation)

Comienza con el manejo de la redirección del authorization code del cliente y el estado de los metadatos del AS que produjo la URL authorization_endpoint. Revisa los fundamentos de Auth Code + PKCE en #319 y los requisitos de RFC 9207; se considera terminado cuando se valida el iss devuelto frente al servidor de autorización iniciador, incluidos los flujos con varios AS.