I have searched the existing issues and discussions.
Problem Description
In the previous version with the commit https://github.com/open-webui/open-webui/commit/217f4daef09b36d3d4cc4681e11d3ebd9984a1a5 an option for passing the OAuth token has been added for the configuration dialogue for External Tools, Connections, etc. but only in the admin settings. For the user settings (accessible via clicking on the username --> "Settings" --> "External Tools") the OAuth option is still missing.
Desired Solution you'd like
It would be convenient, especially for local MCP / tool server development, to have the "OAuth" option in the User Settings (click on the username --> "Settings" --> "External Tools") as well available.
Alternatives Considered
The alternative solution is to configure the tool servers via the admin settings, but during the development phase this is rather tedious as the tool server needs to be externally hosted for Open WebUI to access the server.
Additional Context
No response
Originally created by @koflerm on GitHub (Sep 16, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17480
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
In the previous version with the commit https://github.com/open-webui/open-webui/commit/217f4daef09b36d3d4cc4681e11d3ebd9984a1a5 an option for passing the OAuth token has been added for the configuration dialogue for External Tools, Connections, etc. but only in the admin settings. For the user settings (accessible via clicking on the username --> "Settings" --> "External Tools") the OAuth option is still missing.
<img width="901" height="583" alt="Image" src="https://github.com/user-attachments/assets/d7ecc67d-c4f8-4332-9bea-0b948d431405" />
### Desired Solution you'd like
It would be convenient, especially for local MCP / tool server development, to have the "OAuth" option in the User Settings (click on the username --> "Settings" --> "External Tools") as well available.
### Alternatives Considered
The alternative solution is to configure the tool servers via the admin settings, but during the development phase this is rather tedious as the tool server needs to be externally hosted for Open WebUI to access the server.
### Additional Context
_No response_
This is disabled on purpose due to security reasons. Would be open to discussions here.
<!-- gh-comment-id:3299397344 -->
@tjbck commented on GitHub (Sep 16, 2025):
This is disabled on purpose due to security reasons. Would be open to discussions here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @koflerm on GitHub (Sep 16, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17480
Check Existing Issues
Problem Description
In the previous version with the commit https://github.com/open-webui/open-webui/commit/217f4daef09b36d3d4cc4681e11d3ebd9984a1a5 an option for passing the OAuth token has been added for the configuration dialogue for External Tools, Connections, etc. but only in the admin settings. For the user settings (accessible via clicking on the username --> "Settings" --> "External Tools") the OAuth option is still missing.
Desired Solution you'd like
It would be convenient, especially for local MCP / tool server development, to have the "OAuth" option in the User Settings (click on the username --> "Settings" --> "External Tools") as well available.
Alternatives Considered
The alternative solution is to configure the tool servers via the admin settings, but during the development phase this is rather tedious as the tool server needs to be externally hosted for Open WebUI to access the server.
Additional Context
No response
@tjbck commented on GitHub (Sep 16, 2025):
This is disabled on purpose due to security reasons. Would be open to discussions here.