-
Notifications
You must be signed in to change notification settings - Fork 174
User names are case sensitive #1007
Comments
+1 |
1 similar comment
+1 |
The fix seems very simple, we should take the DN used by the bind action. |
In fact this is not simple to fix at all, but it seems the best option anyway. We will create a migration command for existing users, but it is unlikely that we can automatically merge existing accounts. |
We could/should add a configuration setting for this but I don't think usernames should be treated case-insensitive in general. EDIT: The |
avoid problems with case insensitive ldap users, where user accounts would be created for each login with different upper/lower-case combination fixes graylog-labs/graylog2-web-interface#1007
If users with the same name are found during login (i.e. same letters but different case), an error will be logged during login and logging in will fail. |
In fact after debating the broken solution in the branch above, as well as some alternatives, this seems way too risky for 1.0. |
This will not make it into 1.1 |
+1. We seem to have people routinely log in using different case - and end up with different accounts. Really weird, even I have two accounts: "[email protected]" and "[email protected]" - and yet I can't recall ever logging in with the latter |
We have LDAP integration for Graylog for authentication, and when we log in using different cases, a new user is generated in the system. Graylog is creating new users for different character cases (e.g. askmeaks, ASKMEAKS, askMeaks etc. are all different users). User names should be case in-sensitive.
The text was updated successfully, but these errors were encountered: