Hello,
I'm trying to setup LDAP connection to an AD.
I've made some mistake like forgetting to install php-ldap (BTW it is with a - and not a _ like in the debug message)
Now I've got a "last issue" : I've corrected the filter string thanks to the forum, but on the log I still have a message like this one :
authenticate - Filter error : ldap_search returned no result for filter uid=%samaccountname%
I wasn't able to find this filter (even in parameters.php), and on the site global paramters I have the correct filter.
I guess the info is in the DB, is there a cache or something else to refresh ?
Thanks,
Filter uid=%samaccountname%
It may be uid=%USERNAME%
or samaccountname=%USERNAME%
The %USERNAME% will be replaced with current login user name.
Hello Babynus,
Thanks for your quick feedback.
That's what I've done, it is on the interface setup and in the mysql DB =
sAMAccountName=%USERNAME%
But when I read the log file, I still have an old bad value :
authenticate - Filter error : ldap_search returned no result for filter uid=%samaccountname%)
And I'm not able to identify where uid=... comes from...
Any idea ?
Check if you have same aprameter define in parameters.php file : value in the file overwrites db value.
I've tried to manually add the setting in parameters.php, but it looks like Projeqtor wasn't happy with this : error 500.
I've found that if I use private mode or another browser I no longer have the issue.
Do you know if the filter is pushed to the browser or if apache or PHP has a cache per session ?
Thanks,
Ok, I've found the issue :
there were some php session things remaining with the old filter.
I've check in /var/lib/php/session
and found two files including "uid="
I've deleted both, and now I can log 🙂
Thanks for your help, I can move to the next step
Regards
Hello,
I'm facing the same issue, here's the log trace :
===== TRACE ===== authenticate - Filter error : ldap_search returned no result for filter uid=n.bion)
where n.bion is my AD username
my filter in Projeqtor is uid=%USERNAME% and i tried it with sAMAccountName and it didn't work too.
thanks for helping
The message is clear : there is no user in the Ldap where uid=n.bion
Possibly n.bion is not a uid, or not on the experted root dn.