mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-12 01:54:38 -05:00
Disable authenticaton #161
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#161
Reference in New Issue
Block a user
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?
Originally created by @dezoito on GitHub (Jan 8, 2024).
Is there a way to disable the authentication requirement, so that users don't have to login to use the UI?
Maybe having the admin user authenticating once and then disabling it?
If this entailed chats not being saved that would be alright too.
@tjbck commented on GitHub (Jan 9, 2024):
Hi, Thanks for the suggestion! For security reasons, we do not plan on adding an option to remove the login feature in the near future, so I'll close this issue as not planned for now. However, https://github.com/ollama-webui/ollama-webui-lite provides with the option to use the webui without any of the additional backend functionalities (including auth)!
@sammcj commented on GitHub (Feb 20, 2024):
@tjbck I think this is still needed as an option.
A good example of where Ollama Web UI authentication needs to be disabled is when you're already running the application runs behind another internal authentication service such as Authentik / Okta etc...
This is what I (and a few others I know) do with all our apps for a secure and unified approach but with Ollama Web UI this means logging in twice with two sets of credentials - one of which is no centrally managed.
@justinh-rahb commented on GitHub (Feb 20, 2024):
How will you have chat histories and settings then? This method would need a way to pass some sort of authentication header so that WebUI knows which user to log into.
@sammcj commented on GitHub (Feb 20, 2024):
In my case like I suspect a lot of self-hosters, I just have a single user.
However the standard approach with OAuth2/OpenID (which includes things like Google Workspaces, AzureAD, Authentik, Okta, Auth0 etc...) is to pass an identity token / URL / header or basic auth to applications after successful authentication. You can also have it redirect to a specific URL path (e.g.
<url>/users/<cool@lol.com>) etc...@sammcj commented on GitHub (Feb 20, 2024):
Those are some examples of how people might choose to use Authentik, but I think simply allowing users to disable in-app auth and default to a single user would suffice.
@Chukarslan commented on GitHub (Mar 20, 2024):
Hi, can you detail the steps to disable auth please?
@sammcj commented on GitHub (Mar 20, 2024):
Yeah this is really needed, unfortunately this issue remains closed :(
@tjbck commented on GitHub (Mar 20, 2024):
The exact same issue is open here: #929
Again, we want to emphasise that this is a community project, we encourage you to make a PR!
@sammcj commented on GitHub (Mar 20, 2024):
maybe something like https://github.com/open-webui/open-webui/compare/main...sammcj:open-webui:main
@Chukarslan commented on GitHub (Mar 21, 2024):
This is really cool, I'll check it out thanks @sammcj!
@Chukarslan commented on GitHub (Mar 21, 2024):
Update @sammcj : Still showing the /auth page :(
I tired removing the route in layout.svelte but it keeps bouncing back to auth...
@markg85 commented on GitHub (May 8, 2024):
Ohh security... for f**** sake...
Yes, i get why a login is good for security measures.
But it makes zero sense when running it as a self-hosted service with the intent to just freaking play with ollama.
Somehow so many projects just force down the authentication option where it's clearly intended to be run local for just 1 user (like portainer and grafana, to name a few). And somehow giving the option to disable it is more difficult then to implement an authentication system...
Yeah, that's fucked up.
The intent of this whole project is to run locally so authentication has no place in that.
Sorry for the rant. I'm just annoyed by local projects adding authentication because some people whine about that being "secure and a must-have feature" just to be a pain in the ass for everyone else running it locally as single user, like 99% of your users will!
@justinh-rahb commented on GitHub (May 8, 2024):
@markg85: https://github.com/ollama-webui/ollama-webui-lite