Skip to content

Align upstream OAuth flows with the MCP 2026-07-28 authorization - #7333

Open
madhu-mohan-jaishankar wants to merge 1 commit into
mainfrom
fix/oauth-2026-authorization
Open

madhu-mohan-jaishankar wants to merge 1 commit into
mainfrom
fix/oauth-2026-authorization

Conversation

@madhu-mohan-jaishankar

Copy link
Copy Markdown
Collaborator

Closes #6639

  • Validate the iss parameter on the OAuth callback against the authorization server's issuer before the code is redeemed (RFC 9207). Present means exact string match, absent is refused only when the server advertises iss support, no configured issuer means no check.
  • On a provider error callback with a mismatching iss, replace the provider's error text instead of showing it.
  • Send application_type in dynamic client registration requests. New setting DCR_APPLICATION_TYPE, default auto: native for a loopback redirect URI, web otherwise.
  • When a gateway's OAuth issuer changes, deactivate registered clients bound to the old issuer and log a warning if a static client id is carried over unchanged.
  • Document the 2026-07-28 authorization profile: what is implemented, the deliberate client-token passthrough for auth type none upstreams, and that Client ID Metadata Documents are a follow-up.
  • Tests for each of the above; existing OAuth suites unchanged and passing.

… profile

Signed-off-by: Madhu Mohan Jaishankar <madhu.mohan.jaishankar@ibm.com>
@madhu-mohan-jaishankar madhu-mohan-jaishankar changed the title fix: align upstream OAuth flows with the MCP 2026-07-28 authorization… Align upstream OAuth flows with the MCP 2026-07-28 authorization Oct 23, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Authorization up to the MCP 2026-07-28 authorization spec - ContextForge 1.1

2 participants