K1000: LDAP Filter Issues
Trying to get LDAP setup on my K1000. While all my strings are working find in LDAP browsers, when I run a test connection I keep getting the following error:
Testing "" connection to: on Port:
OK Connection Successful.
OK Setting Protocol Version 3 Successful.
OK Setting LDAP REFERRALS Option 0 Successful.
Error Anonymous Search Bind using LDAP supplied credentials Failed.
Error LDAP Test Failed. Closing connection.
I have the following setup:
The Search Base is as follows:
OU=IT,OU=CorpOU,DC=AD,DC=ACME,DC=com
The Search Filter is as follows:
(&(memberof=CN=Kace Admins Security Group,OU=IT,OU=CorpOU,DC=AD,DC=ACME,DC=com)(sAMAccountName=KBOX_USER))
The LDAP browser returns a username if I replace the KBOX_USER, which tells me the query should be right. But when I replace the KBOX_USER and hit Test LDAP Connection in the LDAP server setup I get an error. If I remove the group reference and just do sAMAccountName=KBOX_USER then the test is successful. There is clearly a syntax issue with my filter (or a system bug) and for the life of me, I just can't find it.
Please help.
Answers (1)
Are you sure of this? I am having the same issue and if I understand correctly, for a production environment samaccountname=KBOX_USER (it will not let you apply without a KBOX_USER there) you would substitute that with the username you want to test and then enter the password for that user next to the Test LDAP Settings button. Is that not correct? I still can't get it to work but I know it will not let me save it with an * instead of KBOX_USER for samaccountname
So this is just one of those silly things.
When you run a test, you must have samaccountname=KBOX_USER. HOWEVER: When running the live LDAP, you need to replace it with Samaccountname=*.
Why? Just the way it works. Anyhow: Give that a shot.
HOWEVER: When looking at my Ldap imports, it is the opposite. When you test you use *, when you go live you use KBOX_USER
Maybe that helps?? - Wildwolfay 10 years ago