[GH-ISSUE #23272] feat: Enabling an integration with OAuth 2.1 at the model level initializes auth flow when user starts chat without session #35467

New Issue

GiteaMirror · 2026-04-25T09:40:47-05:00

GiteaMirror commented

2026-04-25 09:40:47 -05:00

Originally created by @taylorwilsdon on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23272

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

As it stands, you can't toggle a OAuth 2.1 MCP server on a shared custom model because it will error out if a user attempts to use it without having already enabled the tool manually from their Integrations picker. This makes it much more difficult and manual to build shared models that rely on tools with user scoped auth.

Desired Solution you'd like

When an OAuth 2.1 enabled tool is attached to a model, authentication is handled in the same manner as a user toggling on the tool from their chat Integrations menu for the first time - flowing them through when they select that model before they can attempt to send a message.

Alternatives Considered

Some kind of tool status or warning instead, maybe a way to put a banner telling users how to enable it

Additional Context

No response

Originally created by @taylorwilsdon on GitHub (Mar 31, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23272 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description As it stands, you can't toggle a OAuth 2.1 MCP server on a shared custom model because it will error out if a user attempts to use it without having already enabled the tool manually from their Integrations picker. This makes it much more difficult and manual to build shared models that rely on tools with user scoped auth. ### Desired Solution you'd like When an OAuth 2.1 enabled tool is attached to a model, authentication is handled in the same manner as a user toggling on the tool from their chat Integrations menu for the first time - flowing them through when they select that model before they can attempt to send a message. ### Alternatives Considered Some kind of tool status or warning instead, maybe a way to put a banner telling users how to enable it ### Additional Context _No response_

GiteaMirror commented

2026-04-25 09:40:49 -05:00

@taylorwilsdon commented on GitHub (Mar 31, 2026):

As an aside, I'd LOVE a more robust tool status display - when the little wrench icon appears and you click it, you just get a name. Having connection status, auth status, perhaps available tools would be very useful to folks. A little green indicator showing auth in place would be a nice touch.

@taylorwilsdon commented on GitHub (Mar 31, 2026): As an aside, I'd LOVE a more robust tool status display - when the little wrench icon appears and you click it, you just get a name. Having connection status, auth status, perhaps available tools would be very useful to folks. A little green indicator showing auth in place would be a nice touch.

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#35467