github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

issue: ldap creates new user instead of signing in to existing #4311

New Issue
Closed
opened 2025-11-11 15:51:20 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 15:51:20 -06:00
Owner
Copy Link

Originally created by @Bytoft2 on GitHub (Mar 7, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.

Installation Method

Docker

Open WebUI Version

v0.5.20

Ollama Version (if applicable)

No response

Operating System

Debian 12 (bookworm)

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have checked the browser console logs.
  • I have checked the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

When upgrading from v0.5.14 to v0.5.20 users should be able to log in to their existing users with ldap instead of having a new user created.

Actual Behavior

After upgrading from v0.5.14 to v0.5.20, when authenticating using ldap a new user was created instead of logging into the existing user (that was also created using ldap).

Steps to Reproduce

Install version 0.5.14 using ghcp in docker.
Log in using ldap
Do something that should be saved to volume (chat, create model, upload to knowledge)
Upgrade to version 0.5.20 by rerunning the docker container with the new version number
Log in using ldap
User should be a new user instead of the existing.

Logs & Screenshots

N/A

Additional Information

All chats, models and users still existed in the volume, users was just not mapped correctly when logging in. Reverting to the previous version fixed the problem, which could indicate that the logic for matching ldap users to internal users has changed

Originally created by @Bytoft2 on GitHub (Mar 7, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Installation Method Docker ### Open WebUI Version v0.5.20 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 (bookworm) ### Browser (if applicable) _No response_ ### 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 checked the browser console logs. - [x] I have checked the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior When upgrading from v0.5.14 to v0.5.20 users should be able to log in to their existing users with ldap instead of having a new user created. ### Actual Behavior After upgrading from v0.5.14 to v0.5.20, when authenticating using ldap a new user was created instead of logging into the existing user (that was also created using ldap). ### Steps to Reproduce Install version 0.5.14 using ghcp in docker. Log in using ldap Do something that should be saved to volume (chat, create model, upload to knowledge) Upgrade to version 0.5.20 by rerunning the docker container with the new version number Log in using ldap User should be a new user instead of the existing. ### Logs & Screenshots N/A ### Additional Information All chats, models and users still existed in the volume, users was just not mapped correctly when logging in. Reverting to the previous version fixed the problem, which could indicate that the logic for matching ldap users to internal users has changed
GiteaMirror added the bug label 2025-11-11 15:51:20 -06:00
GiteaMirror commented 2025-11-11 15:51:21 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 7, 2025):

Related: https://github.com/open-webui/open-webui/issues/11207

Migration PR welcome!

@tjbck commented on GitHub (Mar 7, 2025): Related: https://github.com/open-webui/open-webui/issues/11207 Migration PR welcome!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4311
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?