-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP default username #1982
Labels
Comments
rodrigok
added a commit
that referenced
this issue
Feb 10, 2016
rodrigok
added a commit
that referenced
this issue
Feb 10, 2016
This was referenced Sep 3, 2020
This was referenced Jan 11, 2022
This was referenced Mar 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While debugging #1967 I encountered a different problem with LDAP.
I have a double surname and thus my email is in the format [email protected].
Email is the filter I'm using for LDAP:
{"filter":"(&(objectClass=*)(mail=#{username}))", "scope":"sub","userDN":"uid=ldaptest,ou=People,dc=dc1,dc=dc2", "password":""}
.And so I'm using my full email to login to Rocket.Chat. However, when I register - RC creates the username by converting the before-@ part of my email to firstname.surname1.surname2 (replaces "-" with ".").
Because I changed the default username I received, to match my email address (I brought back the "-" instead of ".") RC stopped matching my account from LDAP with that in the database and wouldn't allow me to login. LDAP queries were successful, because they were executed using the proper credentials (email & password), but it appears that internally RC is matching the converted username with usernames in the database and in my case - couldn't find any.
The text was updated successfully, but these errors were encountered: