You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Older MCP servers (spec revision 2025-03-26) do not publish /.well-known/oauth-protected-resource. The client must fall back to discovering OAuth metadata directly from the MCP server origin's /.well-known/oauth-authorization-server and, if missing, from the issuer derived by URL convention.
Scope
Order of operations when WWW-Authenticate lacks resource_metadata:
Try /.well-known/oauth-protected-resource at MCP server origin.
Try /.well-known/oauth-authorization-server at MCP server origin.
Fall back to OIDC discovery (/.well-known/openid-configuration).
Track protocol revision negotiated during initialize; only enable fallback chain when the server announced 2025-03-26.
Activity
[Client] Add OAuth authorization to the HTTP transport
chr-hertel commentedon Nov 10, 2026
Solved with #666 - will be part of v0.10.0. It is opt-in with
OAuth::setLegacyDiscovery(true).