[GH-ISSUE #23668] Bug: admin-configured scopes overridden by discovered scopes_supported in static-credential OAuth flow #58706

New Issue

GiteaMirror · 2026-05-05T23:44:12-05:00

GiteaMirror commented

2026-05-05 23:44:12 -05:00

Originally created by @dhruvalgupta2003 on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23668

Summary

In get_oauth_client_info_with_static_credentials, the scope value is unconditionally set from the authorization server's scopes_supported metadata when available. This silently overrides any custom scope string the admin supplied when registering the tool server.

For setups that rely on scope bundling (e.g. registering multiple MCP servers backed by the same Entra AD app, so one consent grants access to all of them — Calendar + Mail + User in a typical M365 deployment), this override means the authorization request ends up with only the generic discovered scopes (e.g. openid profile offline_access) and omits the custom resource scopes. Users get prompted for consent multiple times, or the resulting access token is missing the required audiences.

Location

backend/open_webui/utils/oauth.py around lines 478–481:

scope = None
if oauth_server_metadata and oauth_server_metadata.scopes_supported:
    scope = ' '.join(oauth_server_metadata.scopes_supported)

Impact

Breaks the "one consent, N MCP servers" pattern for M365 / Entra ID integrations.
Silently drops admin-chosen scopes with no warning.

Suggested fix

Prefer the admin-provided scope if one was supplied; fall back to discovered scopes_supported only when no explicit scope exists. Log when metadata-discovered scopes are being used so the behaviour is visible.

Originally created by @dhruvalgupta2003 on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23668 ### Summary In `get_oauth_client_info_with_static_credentials`, the scope value is unconditionally set from the authorization server's `scopes_supported` metadata when available. This silently overrides any custom scope string the admin supplied when registering the tool server. For setups that rely on **scope bundling** (e.g. registering multiple MCP servers backed by the same Entra AD app, so one consent grants access to all of them — Calendar + Mail + User in a typical M365 deployment), this override means the authorization request ends up with only the generic discovered scopes (e.g. `openid profile offline_access`) and omits the custom resource scopes. Users get prompted for consent multiple times, or the resulting access token is missing the required audiences. ### Location `backend/open_webui/utils/oauth.py` around lines 478–481: ```python scope = None if oauth_server_metadata and oauth_server_metadata.scopes_supported: scope = ' '.join(oauth_server_metadata.scopes_supported) ``` ### Impact - Breaks the "one consent, N MCP servers" pattern for M365 / Entra ID integrations. - Silently drops admin-chosen scopes with no warning. ### Suggested fix Prefer the admin-provided scope if one was supplied; fall back to discovered `scopes_supported` only when no explicit scope exists. Log when metadata-discovered scopes are being used so the behaviour is visible.

GiteaMirror closed this issue

2026-05-05 23:44:14 -05:00

GiteaMirror commented

2026-05-05 23:44:18 -05:00

@tjbck commented on GitHub (Apr 17, 2026):

Likely addressed with 349ea4ea9e.

Dynamic Oauth2.1 should be used in general.

@tjbck commented on GitHub (Apr 17, 2026): Likely addressed with 349ea4ea9e577f2cbfb4917ef5f52e5ac53c5b70. Dynamic Oauth2.1 should be used in general.

GiteaMirror commented

2026-05-05 23:44:19 -05:00

@p-ob commented on GitHub (Apr 22, 2026):

Was this issue actually resolved in 349ea4ea9e?

Per https://datatracker.ietf.org/doc/html/rfc6749#section-3.3,

If the client omits the scope parameter when requesting
authorization, the authorization server MUST either process the
request using a pre-defined default value or fail the request
indicating an invalid scope. The authorization server SHOULD
document its scope requirements and default value (if defined).

I agree that DCR or CIMD should be supported by IdPs, but for those IdPs that still require static client configuration, the ability for an admin in Open WebUI to be able to specify those scopes for static clients seems valuable.

Edit: On review of the MCP spec, I think the original behavior for when scopes aren't defined was what was originally implemented: https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#scope-selection-strategy

Use scope parameter from the initial WWW-Authenticate header in the 401 response, if provided
If scope is not available, use all scopes defined in scopes_supported from the Protected Resource Metadata document, omitting the scope parameter if scopes_supported is undefined.

@p-ob commented on GitHub (Apr 22, 2026): Was this issue actually resolved in https://github.com/open-webui/open-webui/commit/349ea4ea9e577f2cbfb4917ef5f52e5ac53c5b70? Per <https://datatracker.ietf.org/doc/html/rfc6749#section-3.3>, > If the client omits the scope parameter when requesting authorization, the authorization server MUST either process the request using a pre-defined default value or fail the request indicating an invalid scope. The authorization server SHOULD document its scope requirements and default value (if defined). I agree that DCR or CIMD should be supported by IdPs, but for those IdPs that still require static client configuration, the ability for an admin in Open WebUI to be able to specify those scopes for static clients seems valuable. **Edit:** On review of the MCP spec, I think the original behavior for when scopes aren't defined was what was originally implemented: <https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#scope-selection-strategy> > Use scope parameter from the initial WWW-Authenticate header in the 401 response, if provided If scope is not available, use all scopes defined in scopes_supported from the Protected Resource Metadata document, omitting the scope parameter if scopes_supported is undefined.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#58706