You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2024. It is now read-only.
I've an strange issue when binding to an Active Directory Server. I am trying to authenticate the user using ldapjs.
This is my code which works fine with most users...
`
var connectionSettings = {
url: LDAP_URL,
bindDN: "domain\ipindado",
bindCredentials: LDAP_ADMIN_PASSWORD
};
The strange thing is that I'm not using the DN for binding, I am using samaccountname with domain "domain\jigonzalez" which works fine for most of the users.
And we have also testested removing the special characters in the Active Directory and authentication works fine for these users after removing the characters.
Did any body faced something similar?
Thanks and Best regards.
The text was updated successfully, but these errors were encountered:
Hello...
I've an strange issue when binding to an Active Directory Server. I am trying to authenticate the user using ldapjs.
This is my code which works fine with most users...
`
var connectionSettings = {
url: LDAP_URL,
bindDN: "domain\ipindado",
bindCredentials: LDAP_ADMIN_PASSWORD
};
`
Note that I am making the simple binding using "domain\samaccountname" instead of DistinguisedName
But I have some issues with some specific users, when the DistinguisedName conmtains special characters like áéíóú as for example
"dn": "CN=Jos\c3\a9 Ignacio Gonzalez,OU=Externos_O365,OU=BU,DC=domain,DC=local",
The strange thing is that I'm not using the DN for binding, I am using samaccountname with domain "domain\jigonzalez" which works fine for most of the users.
And we have also testested removing the special characters in the Active Directory and authentication works fine for these users after removing the characters.
Did any body faced something similar?
Thanks and Best regards.
The text was updated successfully, but these errors were encountered: