Hi Sidharth,
Greatly appreciate your continuous help here. Just to have the entire config in one message here. I installed and configured the AD/LDAP connector without much problems, my config didn’t complain, i.e, the connector was able to connect to my LDAP (eDirectory). The Troubleshooter also was able to find the one test user:
Again, NLTEST failed but I wasn’t connecting to AD here, so I ignored this error. I did update the config.json to provide both “cn” and “mail” as possible login option:
Restarting the connector, I still failed the Search:
Regarding your LDAP_BASE question, yes, I have the domain correct, here’s the LDAP entry that I use to test this (cn=user1), you can see that the hierarchy is cn=user1,ou=people,o=demo:
I even looked into the connector code myself: ad-ldap-connector/users.js at 2f323447f5c5ecc010a98a468eb07475e9604558 · auth0/ad-ldap-connector · GitHub and I don’t see the issue with replacing “username” with what I put in, the “cn” attribute value:
Users.prototype.getByUserName = function (userName, callback) {
var self = this;
var opts = {
scope: ‘sub’,
filter: nconf.get(‘LDAP_USER_BY_NAME’).replace(/{0}/g, userName)
};
FYI, I have no issue integrating this LDAP with another vendor’s agent, so I know the LDAP itself is valid.
The question is why is it working fine in Troubleshooter but not Search? If I can get Search to work, then I know it’ll work with the default app. Any ideas are much appreciated.
Thanks,
Karmen