-
Notifications
You must be signed in to change notification settings - Fork 15
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
Issues with Users that have a "Umlaut" eg. Ö or ß #142
Comments
I have investigated. |
found it... and fixed in 5.0.1 |
building 5.0.1 beta now |
I had to decode instead, ldap return encoded Distinguished name and to bind ldap, I must send utf8, so had to build an unescape function. |
Hello @ansibleguy76 Thanks for your workaround, but it doesn't work for these cases
I have read the test file available here: https://github.com/ldapjs/dn/blob/master/lib/utils/escape-value.test.js I have written a simple version, which I will share with you here const unescapeLdapDnString = input => {
// Convert \\xXX to %XX
const convertedStr = input.replace(/\\([0-9A-Fa-f]{2})/g, (_, hex) => '%' + hex);
return decodeURIComponent(convertedStr);
}; Have a nice day, |
Describe the bug
I have configured authentication via an Active Directory Server. Users without a german "Umlaut" can login without any problems.
But users with an "Umlaut" in there CN getting "Ldap: Invalid Credentials" as a response on the login page.
It has been double checked with two users having this issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User should login without any errors.
Version
ansibleforms v5.0.0
Deployment
Deployed ansibleforms with :
Additional context
Logs only shows error: Error connecting to
ldap : Invalid Credentials but credentials
are correct.Full DN from user account look similar than this
CN=<here is sAMAccountName>_(<forename>_<surname>),OU=user,OU=<censored>,DC=<censored>,DC=<censored>,DC=de
as<surname>
contains an "Ö"The text was updated successfully, but these errors were encountered: