MCP OAuth: Okta Scopes, Upstream Compatibility, and Clearer Pages
OAuth for MCP works with more identity providers and upstream servers. You can now declare the scopes clients should request, connect the MCP Gateway to upstreams whose OAuth metadata doesn’t line up with their URLs, and give users clearer pages when a browser connection succeeds or fails.
Advertise scopes for your MCP server
The OAuthProtectedResourcePlugin has a new scopesSupported option. The
gateway publishes those scopes in its protected resource metadata and, for OAuth
policies with oAuthResourceMetadataEnabled, in the scope parameter of the
401 challenge. MCP clients then request exactly the scopes you list.
This makes Okta custom authorization servers work with MCP clients. Without declared scopes, clients fell back to every scope Okta advertises, a combination Okta rejects. See Okta setup for MCP OAuth for the full walkthrough.
Connect to more upstream OAuth providers
The MCP Gateway connects to more upstream MCP servers that use OAuth:
- Metadata discovery falls back to OpenID Connect. When a provider doesn’t
serve OAuth authorization server metadata, the gateway uses its
/.well-known/openid-configurationdocument instead, which covers providers such as Salesforce. - Opt out of the issuer check per upstream. Set
skipIssuerMetadataValidationwhen a provider’s metadata reports anissuerthat differs from the authorization server URL it advertises, as ServiceNow does. - Opt out of resource indicator validation per upstream. Set
skipResourceIndicatorValidationwhen an upstream behind a CDN hostname, path rewrite, or regional subdomain advertises aresourcethat doesn’t match the URL you call.
Both opt-outs are off by default and apply to a single upstream connection. Enable one only after confirming the mismatch with the provider. See OAuth metadata validation for details.
Clearer connection pages
The browser pages users see while connecting an upstream are redesigned. When a connection fails, the page shows what went wrong, numbered next steps, and a reference box with the error code, request ID, and time to share with an admin. Technical details, such as the suggested fix and the stage that failed, appear once in their own section. More upstream setup failures, including issuer mismatches and rejected client registrations, now come with a specific explanation instead of a generic error. The Connection complete page follows the same layout.
Getting started
See the
OAuth Protected Resource Plugin reference
for scopesSupported, and
Per-user OAuth to upstream MCP servers
for how the MCP Gateway connects to upstreams.