github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 15:54:15 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

enh: [SSO] Github OAuth2 support #3301

New Issue
Closed
opened 2025-11-11 15:28:36 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 15:28:36 -06:00
Owner
Copy Link

Originally created by @Tryanks on GitHub (Jan 16, 2025).

Is your feature request related to a problem? Please describe.
The current OAuth2 only supports OIDC login with a well-known URL, such as https://accounts.google.com/.well-known/openid-configuration.
This makes the essence of all OAuth2 logins inherently OIDC logins. At the same time, this also makes it difficult to add support for Github OAuth2 to the same list, because Github OAuth does not provide a .well-known compatible solution.

Describe the solution you'd like
An unreasonable solution would be to move all current OAuth2 authentications under the OIDC category and establish a dedicated authentication implementation for OAuth2.
A slightly more reasonable solution would be to implement a separate authentication method for Github and directly add it to the OIDCs environment variables list in the configuration options.

Describe alternatives you've considered
Using oauth2-proxy can simplify enabling open webui to support Github authentication, and this is the solution I am currently using. However, its consistency is not ideal and can only be considered a temporary measure.

Additional context
I am interested in providing a PR for this feature, but the issue lies in the project structure. To support Github OAuth2, code reuse is obviously impossible, and the goal can only be achieved by writing a substantial amount of dedicated code for it.
I hope that the Members and everyone else can share their views on this requirement in this discussion.

Originally created by @Tryanks on GitHub (Jan 16, 2025). **Is your feature request related to a problem? Please describe.** The current OAuth2 only supports OIDC login with a well-known URL, such as https://accounts.google.com/.well-known/openid-configuration. This makes the essence of all OAuth2 logins inherently OIDC logins. At the same time, this also makes it difficult to add support for Github OAuth2 to the same list, because Github OAuth does not provide a `.well-known` compatible solution. **Describe the solution you'd like** An unreasonable solution would be to move all current *OAuth2* authentications under the OIDC category and establish a dedicated authentication implementation for OAuth2. A slightly more reasonable solution would be to implement a separate authentication method for Github and directly add it to the OIDCs environment variables list in the configuration options. **Describe alternatives you've considered** Using oauth2-proxy can simplify enabling `open webui` to support Github authentication, and this is the solution I am currently using. However, its consistency is not ideal and can only be considered a temporary measure. **Additional context** I am interested in providing a PR for this feature, but the issue lies in the project structure. To support Github OAuth2, code reuse is **obviously** impossible, and the goal can only be achieved by writing a substantial amount of dedicated code for it. I hope that the Members and everyone else can share their views on this requirement in this discussion.
GiteaMirror commented 2025-11-11 15:28:43 -06:00
Author
Owner
Copy Link

@AzizDXT commented on GitHub (Jan 17, 2025):

Also Google :)

@AzizDXT commented on GitHub (Jan 17, 2025): Also Google :)
GiteaMirror commented 2025-11-11 15:28:44 -06:00
Author
Owner
Copy Link

@Tryanks commented on GitHub (Jan 17, 2025):

Also Google :)

The current Open WebUI inherently supports GOOGLE :)
https://docs.openwebui.com/features/sso#google

@Tryanks commented on GitHub (Jan 17, 2025): > Also Google :) The current Open WebUI inherently supports GOOGLE :) https://docs.openwebui.com/features/sso#google
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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#3301
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?