mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #17917] issue: oauth user signup flow breaking due to generated password crossing 72 bytes #18436
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 @thenicekat on GitHub (Sep 30, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17917
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.32
Ollama Version (if applicable)
No response
Operating System
ubuntu
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
It should create a new account and move on.
4d7fddaf7e/backend/open_webui/utils/oauth.py (L1225)Actual Behavior
Error during OAuth process: password cannot be longer than 72 bytes, truncate manually if necessary (e.g. my_password[:72])
This error is coming during oauth signup flow. I am not sure what changed here. All new signups are breaking because of this. I am not sure why this even hits
4d7fddaf7e/backend/open_webui/routers/auths.py (L596)that particular endpoint. I would assume oauth.py is not making an api call to /signup but i am not sure.Steps to Reproduce
On any oauth flow, try to signup without a pre created account.
Logs & Screenshots
Error during OAuth process: password cannot be longer than 72 bytes, truncate manually if necessary (e.g. my_password[:72])
Additional Information
No response
@thenicekat commented on GitHub (Sep 30, 2025):
It's happening consistently on even without oauth:
This was me running a new openwebui image locally.
@tjbck commented on GitHub (Sep 30, 2025):
@silentoplayz Are you able to reproduce here? I'm currently unable.
@thenicekat commented on GitHub (Sep 30, 2025):
huh? weird, um, should openwebui image require anything else out of the box? I have always used it this way and it always worked before.
@tjbck commented on GitHub (Sep 30, 2025):
We have not changed anything here for our latest release, something else might be playing a role here.
@silentoplayz commented on GitHub (Sep 30, 2025):
@tjbck I am able to reproduce with a long password being used on signup within the UI. Below is the password I attempted to create an account/sign up with:
The following notification toast is displayed on-click of

Create Account:Error on backend:
@thenicekat commented on GitHub (Sep 30, 2025):
I just used
abcas password@silentoplayz commented on GitHub (Sep 30, 2025):
@thenicekat I can't reproduce with just

abcas the password.@thenicekat commented on GitHub (Sep 30, 2025):
https://github.com/user-attachments/assets/c1f7b26a-f0b8-4347-a537-828349d945d1
@thenicekat commented on GitHub (Sep 30, 2025):
When I run backend locally (code on main), I could create an account, I am not sure what changed or what is going wrong in the docker image but, if I hit the server when I am running the docker image, it still fails.
@thenicekat commented on GitHub (Sep 30, 2025):
Looks like it's coming from inside bcrypt.
So, openwebui backend passes it through but bcrypt fails it which is leading to different errors from me and @silentoplayz's side.
https://github.com/pyca/bcrypt/issues/1082
Possibly related.
@thenicekat commented on GitHub (Sep 30, 2025):
Confirmed: Downgrading bcrypt fixes it. I had unpinned versions of some of the libraries to remove vulnerabilities but maybe unpinning bcrypt was a bad idea. We can close this issue. Sorry for the trouble.
@thenicekat commented on GitHub (Oct 1, 2025):
https://github.com/pyca/bcrypt/issues/1079
Looks like they are encouraging us to stop using passlib. Is it okay if I make a PR removing passlib and using bcrypt directly? @tjbck @silentoplayz
@tjbck commented on GitHub (Oct 2, 2025):
Should be addressed with
ebce0578e6in dev!@silentoplayz commented on GitHub (Oct 8, 2025):
@thenicekat Has
ebce0578e6addressed the issue for you?@thenicekat commented on GitHub (Oct 8, 2025):
I downgraded it, that definitely worked. I did not check any latest release yet.