LDAP issues after updating to 4.2.0.32840
AnsweredGreetings,
It seems that since the most recent update, we are having issues fetching users from LDAP? This is for the Cambodia system. We hadn't made any LDAP/directory related changes recently, and I've walked back through the LDAP setup documents and I cannot see the specific issue. If I use a LDAP browser with the same settings, I'm able to fetch users with no problem.
Things are working, except my search filter. Previously, this was working fine with two systems:
(&(objectClass=inetOrgPerson)(memberOf=cn=LDAP - Security Cameras,ou=Users,o=5aa8a63a4b222f4cdeec4011,dc=jumpcloud,dc=com))
But now it does not fetch any users. I can test this externally through LDAP browsers and it is working fine. And again, nothing changed with our configuration? Did something change on the NX side related to LDAP?
If I remove the search filter it can pull all 16 users fine... except for this system we need to limit the users by LDAP group.
-
Hi Luke McFadden,
I'm not able to reproduce your case on my 4.2 server with our LDAP server of jumpcloud.
Could you help to collect the server log with the VERBOSE logging level while fetching the user from LDAP server? (Please refer to the instruction in this article)Thank you for your cooperation.
-
Hi Luke McFadden,
Just checking in to make sure you received our response as it has been a while since we have heard from you. Please let us know if you still need help by responding to this email. We are eager to resolve your question as soon as possible.
-
Wendy Chuang. Sorry for the slow reply. The issue did end up being with my LDAP provider, so things are working as they should now.
-
Hi Luke McFadden,
Good to hear everything is working fine now.
Thanks for your update :-)
Please sign in to leave a comment.
Comments
4 comments