mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
issue: OIDC login flow stucks after callback #5534
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 @aidarsvd on GitHub (Jun 13, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.14
Ollama Version (if applicable)
No response
Operating System
macOS Sequoia
Browser (if applicable)
Chrome 137.0.7151.104
Confirmation
README.md.Expected Behavior
After completing a successful login via a compliant OIDC provider (which correctly returns all required tokens and endpoints, including /openid-configuration, /token, /userinfo, and /certs), the Open WebUI frontend should properly handle the callback and direct the user to the main application interface.
The authenticated user should be created or updated in the database with the correct data, and automatically logged into the system without encountering frontend routing errors like Not found: //auth.
Actual Behavior
After a successful login with the OIDC provider, the user is redirected back to the Open WebUI callback endpoint, which correctly processes the /token, /userinfo, and /certs requests. The backend responds with a 307 redirect as expected.
However, the frontend does not handle the redirect properly. Instead of logging the user in and routing to the main interface, the app throws a routing error in the console and returns to the auth page again:
Steps to Reproduce
Launch the application and initiate login.

Complete authentication on the configured OIDC provider.
After the redirection, you end up back on the login page with the path
/auth?redirect=%2F%2FauthLogs & Screenshots
Logs from the Browser console after redirection:
Logs from the container
Additional Information
OID Configuration response
Container database
In the database, user was created successfully. In the table
authrecord appeared with correct data and status=1. Same for tableuser@ShineQi commented on GitHub (Jun 13, 2025):
I'm having the same issue with Azure AD login, it seems the login was success, but browser side redirected to //auth, duplicated backslash
@Nortrix0 commented on GitHub (Jun 13, 2025):
I also ran into this, oddly enough my coworker has a similar setup but doesn't have this issue. It seems to be fixed in this Merge Request so hopefully it'll be pushed to a release soon.
https://github.com/open-webui/open-webui/pull/14943
@jk-f5 commented on GitHub (Jun 13, 2025):
FYI: you can fix the issue inline with your docker command if you want.. Basically use sed to replace the line that causes auth to fail, then start up open-webui. Example:
@aidarsvd commented on GitHub (Jun 16, 2025):
fixed in v0.6.15
@wllianwd commented on GitHub (Jun 25, 2025):
I'm having the same issue after updating (from v0.6.10), even with v0.6.15:
@jk-f5 commented on GitHub (Jun 25, 2025):
This is not the same issue.