Client Binding Possible Issue?
See original GitHub issueI’m going to start off by saying that I’m not LDAP expert so this may be user error, if so please advise.
I’ve been using other libraries (https://github.com/jeremycx/node-LDAP) for LDAP authentication but due to various issues with them would like to move away from them. Anyways, the binding in that would allow me to provide the users network login information (which is in the LDAP as sAMAccountName) in a method of binding. I’d pretty much call it like
client.SimpleBind("Username", "Password", function (success) { ... })
Anyways, the bind method here requires me to provide a DN in the first variable, which I’m not sure what to provide. I’ve tried it without the “DN=” and that doesn’t work. The following does not work either.
client.bind('sAMAccountName=Username', 'Password', function(err) {
assert.ifError(err);
});
For what it’s worth, using tools like JXplorer I can connect using Username/Password without specifying a DN and it works. When I search for the Username it will bring it up by matching the sAMSAccountName.
Issue Analytics
- State:
- Created 12 years ago
- Comments:11 (5 by maintainers)
So with OepnLDAP
Domain\Username
in the-D
works? Ok, that tells me what I need to know.@rrobe53 It is not clear to me how you solved the Issue. I just wish a code snippet with the final solution was in here. Update
I was able to use node-activedirectory to authenticate user credentials (bind) successfully. https://github.com/typ90/meteor-accounts-ldap/issues/8#issuecomment-162632091
Thanks