Originally created by @codespg on GitHub (Mar 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11956
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.5.18
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu 22
### Browser (if applicable)
Chrome
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have listed steps to reproduce the bug in detail.
### Expected Behavior
I have Setup Reverse proxy for Open Web UI and Normal Login works fine.
Added below parameters for HTTP Header Authentication for SSO Setup
-e ENABLE_LOGIN_FORM:False
-e WEBUI_AUTH_TRUSTED_EMAIL_HEADER:X-Remote-User
-e WEBUI_AUTH_TRUSTED_NAME_HEADER:X-First-Name
Expecting below beheaviour:
1. On opening Open Web UI URL, Identifies WEBUI_AUTH_TRUSTED_EMAIL_HEADER and Login if the email user already present
2. If User does not present or Valid Email not found in WEBUI_AUTH_TRUSTED_EMAIL_HEADER, Error as User not found/Invalid user.
### Actual Behavior
1. Login page shows up
2. No Option to choose SSO
### Steps to Reproduce
Run docker with below env variables
docker run -d -e OAUTH_MERGE_ACCOUNTS_BY_EMAIL:True -e WEBUI_SESSION_COOKIE_SAME_SITE:lax -e WEBUI_AUTH_COOKIE_SAME_SITE:lax -e ENABLE_LOGIN_FORM:False -e WEBUI_AUTH_TRUSTED_EMAIL_HEADER:X-Remote-User -e WEBUI_AUTH_TRUSTED_NAME_HEADER:X-First-Name -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:main
### Logs & Screenshots
[browser_console_log.log](https://github.com/user-attachments/files/19404144/browser_console_log.log)
### Additional Information
[browser_har_file.har.zip](https://github.com/user-attachments/files/19404147/browser_har_file.har.zip)
GiteaMirror
added the bug label 2026-05-18 00:50:09 -05:00
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 @codespg on GitHub (Mar 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11956
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.5.18
Ollama Version (if applicable)
No response
Operating System
Ubuntu 22
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
I have Setup Reverse proxy for Open Web UI and Normal Login works fine.
Added below parameters for HTTP Header Authentication for SSO Setup
-e ENABLE_LOGIN_FORM:False
-e WEBUI_AUTH_TRUSTED_EMAIL_HEADER:X-Remote-User
-e WEBUI_AUTH_TRUSTED_NAME_HEADER:X-First-Name
Expecting below beheaviour:
Actual Behavior
Steps to Reproduce
Run docker with below env variables
docker run -d -e OAUTH_MERGE_ACCOUNTS_BY_EMAIL:True -e WEBUI_SESSION_COOKIE_SAME_SITE:lax -e WEBUI_AUTH_COOKIE_SAME_SITE:lax -e ENABLE_LOGIN_FORM:False -e WEBUI_AUTH_TRUSTED_EMAIL_HEADER:X-Remote-User -e WEBUI_AUTH_TRUSTED_NAME_HEADER:X-First-Name -p 3000:8080 -v open-webui:/app/backend/data --name open-webui ghcr.io/open-webui/open-webui:main
Logs & Screenshots
browser_console_log.log
Additional Information
browser_har_file.har.zip