mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
A user with the email ... already exists but with different credentials #1453
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 @oden08 on GitHub (Nov 15, 2019).
Describe the bug
All users nowe get logging in all of a sudden I get the error "A user with the email ... already exists but with different credentials".
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected behavior is normal login
Screenshots
Your Configuration (please complete the following information):
Additional context
Add any other context about the problem here.
@ssddanbrown commented on GitHub (Nov 16, 2019):
Hi @oden08,
Can you confirm what authentication systems are active and which one you used to show the error message above?
LDAP? Standard Email+Password? Google?
@oden08 commented on GitHub (Nov 18, 2019):
Sorry for the delay, we are using LDAP.
@oden08 commented on GitHub (Nov 19, 2019):
Is there a log I can look at? Could my user database have gotten messed up? I've checked that my LDAP user is active and the password hasn't changed.
@oden08 commented on GitHub (Nov 19, 2019):
Ok, weird thing, ran some sql statements against the database and now we are able to connect in.
@Mikuz commented on GitHub (Feb 25, 2020):
Hello there, I have this same problem.
My config:
LDAP_SERVER=172.16.100.2:389
LDAP_BASE_DN=ou=Pracownicy,ou=Users,ou=Pxxx,dc=Pxxx,dc=pl
LDAP_DN=xxxx
LDAP_PASS=xxxx
LDAP_USER_FILTER=(|(sAMAccountName=${user})(userPrincipalName=${user}))
LDAP_VERSION=false
LDAP_ID_ATTRIBUTE=mail
LDAP_EMAIL_ATTRIBUTE=mail
LDAP_DISPLAY_NAME_ATTRIBUTE=cn
When I login first time (on clear bookstack) using Ldap there are zero problems, but when I try to login again, it tries to create again a new account and it fails - because email is already taken.
@ssddanbrown commented on GitHub (Feb 28, 2020):
@Mikuz If you're still facing issues please open a new issue since this one is closed, and the details required to create an issue will be helpful and may differ in your case.