github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 23:21:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21633] issue: Oauth 2.1 tools no longer showing up in UI #90281

New Issue
Closed
opened 2026-05-15 15:29:21 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-15 15:29:21 -05:00
Owner
Copy Link

Originally created by @ryan-pip on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21633

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Other

Open WebUI Version

v0.8.3

Ollama Version (if applicable)

No response

Operating System

Linux (on AWS Fargate)

Browser (if applicable)

Arc + Safari

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

All tools the user has access to can be selected and deselected from the UI

Actual Behavior

Tools configured with OAuth 2.1 authentication are not appearing in the model selection interface either at system model or workspace models. The tools are still attached to the model and working. They just don't appear in the UI. These were previously showing prior to the last version update.

Tools can be seen in the network call:

[
    {
        "id": "server:mcp:rovo",
        "user_id": "server:mcp:rovo",
        "name": "Atlassian Rovo",
        "meta": {
            "description": "Atlassian Rovo MCP Server for access to confluence, jira, etc",
            "manifest": {}
        },
        "access_grants": [],
        "updated_at": 1771558590,
        "created_at": 1771558590,
        "user": null,
        "authenticated": true
    },
    {
        "id": "server:mcp:context7",
        "user_id": "server:mcp:context7",
        "name": "Context7",
        "meta": {
            "description": "Context7 brings up-to-date, version-specific documentation and code examples directly into your AI coding assistant. That means no more outdated code or hallucinated APIs.",
            "manifest": {}
        },
        "access_grants": [],
        "updated_at": 1771558590,
        "created_at": 1771558590,
        "user": null
    },
]

The can also be seen in the model json:

    "toolIds": [
      "server:mcp:rovo",
      "server:mcp:context7",
    ],

Steps to Reproduce

Install two mcp type external tools.

  1. One using Oauth 2.1.
  2. One using a api token or custom header.
    If both show up add them to a model, then go authenticate it then return and see if it still shows up.

Logs & Screenshots

There are no error messages or logs

Additional Information

I believe for some reason the UI is filtering out tools where the tools shows as authenticated: true

Originally created by @ryan-pip on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21633 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Other ### Open WebUI Version v0.8.3 ### Ollama Version (if applicable) _No response_ ### Operating System Linux (on AWS Fargate) ### Browser (if applicable) Arc + Safari ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior All tools the user has access to can be selected and deselected from the UI ### Actual Behavior Tools configured with OAuth 2.1 authentication are not appearing in the model selection interface either at system model or workspace models. The tools are still attached to the model and working. They just don't appear in the UI. These were previously showing prior to the last version update. Tools can be seen in the network call: ``` [ { "id": "server:mcp:rovo", "user_id": "server:mcp:rovo", "name": "Atlassian Rovo", "meta": { "description": "Atlassian Rovo MCP Server for access to confluence, jira, etc", "manifest": {} }, "access_grants": [], "updated_at": 1771558590, "created_at": 1771558590, "user": null, "authenticated": true }, { "id": "server:mcp:context7", "user_id": "server:mcp:context7", "name": "Context7", "meta": { "description": "Context7 brings up-to-date, version-specific documentation and code examples directly into your AI coding assistant. That means no more outdated code or hallucinated APIs.", "manifest": {} }, "access_grants": [], "updated_at": 1771558590, "created_at": 1771558590, "user": null }, ] ``` The can also be seen in the model json: ``` "toolIds": [ "server:mcp:rovo", "server:mcp:context7", ], ``` ### Steps to Reproduce Install two mcp type external tools. 1. One using Oauth 2.1. 2. One using a api token or custom header. If both show up add them to a model, then go authenticate it then return and see if it still shows up. ### Logs & Screenshots There are no error messages or logs ### Additional Information I believe for some reason the UI is filtering out tools where the tools shows as `authenticated: true`
GiteaMirror added the bug label 2026-05-15 15:29:21 -05:00
GiteaMirror commented 2026-05-15 15:29:24 -05:00
Author
Owner
Copy Link

@PedroFCM commented on GitHub (Feb 20, 2026):

+1 Reproducing on v0.8.3 with OAuth 2.1 MCP

<!-- gh-comment-id:3932309294 --> @PedroFCM commented on GitHub (Feb 20, 2026): +1 Reproducing on v0.8.3 with OAuth 2.1 MCP
GiteaMirror commented 2026-05-15 15:29:25 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Feb 20, 2026):

Unable to reproduce @Classic298 could you confirm?

<!-- gh-comment-id:3937551628 --> @tjbck commented on GitHub (Feb 20, 2026): Unable to reproduce @Classic298 could you confirm?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#90281
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?