Pulled down the repo and am running the app locally.
Environment
Open WebUI Version: 0.5.7
Confirmation:
[x ] I have read and followed all the instructions provided in the README.md.
[x ] I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
[x ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
After logging into the app with LDAP, users should enter the app without issue.
Actual Behavior:
After logging into the app with LDAP, users see a blank white screen. Need to refresh page to see the app.
Description
Bug Summary:
In the endpoint to authenticate with LDAP, the new user permissions data is not returned in the response. As a result, the UI is erroring out because it is looking for those permissions.
Refreshing the page fixes this issue because the next time the app is hit, it authenticates using the token instead of going through the LDAP endpoint.
Reproduction Details
Steps to Reproduce:
Enable LDAP authentication on the app.
Sign into the app using LDAP
See a blank screen
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
Fix needs to be made in auths.py in the "/ldap" endpoint. The user permissions needs to be returned (like how the other auth endpoints are doing it)
Originally created by @bunnerz-king on GitHub (Jan 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9011
# Bug Report
---
## Installation Method
Pulled down the repo and am running the app locally.
## Environment
- **Open WebUI Version:** 0.5.7
**Confirmation:**
- [x ] I have read and followed all the instructions provided in the README.md.
- [x ] I am on the latest version of both Open WebUI and Ollama.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
- [x ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
After logging into the app with LDAP, users should enter the app without issue.
## Actual Behavior:
After logging into the app with LDAP, users see a blank white screen. Need to refresh page to see the app.
## Description
**Bug Summary:**
In the endpoint to authenticate with LDAP, the new user permissions data is not returned in the response. As a result, the UI is erroring out because it is looking for those permissions.
Refreshing the page fixes this issue because the next time the app is hit, it authenticates using the token instead of going through the LDAP endpoint.
## Reproduction Details
**Steps to Reproduce:**
1) Enable LDAP authentication on the app.
2) Sign into the app using LDAP
4) See a blank screen
## Logs and Screenshots
**Browser Console Logs:**
[Include relevant browser console logs, if applicable]
**Screenshots/Screen Recordings (if applicable):**
[Attach any relevant screenshots to help illustrate the issue]
## Additional Information
Fix needs to be made in auths.py in the "/ldap" endpoint. The user permissions needs to be returned (like how the other auth endpoints are doing it)
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 @bunnerz-king on GitHub (Jan 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9011
Bug Report
Installation Method
Pulled down the repo and am running the app locally.
Environment
Confirmation:
Expected Behavior:
After logging into the app with LDAP, users should enter the app without issue.
Actual Behavior:
After logging into the app with LDAP, users see a blank white screen. Need to refresh page to see the app.
Description
Bug Summary:
In the endpoint to authenticate with LDAP, the new user permissions data is not returned in the response. As a result, the UI is erroring out because it is looking for those permissions.
Refreshing the page fixes this issue because the next time the app is hit, it authenticates using the token instead of going through the LDAP endpoint.
Reproduction Details
Steps to Reproduce:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Screenshots/Screen Recordings (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Additional Information
Fix needs to be made in auths.py in the "/ldap" endpoint. The user permissions needs to be returned (like how the other auth endpoints are doing it)
@tjbck commented on GitHub (Jan 28, 2025):
PR Welcome!