On Thu, Jun 11, 2009 at 12:06 PM, Dieter Kluenter<die...@dkluenter.de> wrote: > Bryan Irvine <sparcta...@gmail.com> writes: > >> I got around those problems but I'm still having problems binding to the DB. >> >> The script basically logs in and does a search for itself to make sure >> all is well. >> >> I cannot bind with the credentials given me by the LDAP server admin, >> but the search shows that the user is there. However if I add more >> leading underscores _or remove it, I still get a result. If I add >> extra letters such as _lldap.... then it fails the search. >> >> Is the leading underscore causing me grief on the bind as well? >> >> +++++++++++++++++++ >> code: >> $check_CN = "_ldapmonitor_test"; >> >> my $problem = $ldaps->bind ( >> 'cn=_ldapmonitor_test,ou=service,ou=users,ou=admin,o=noah', >> password=> 'oursupersecretpassword' >> ); >> > > perldoc Net::LDAPS > capath is missing.
I don't see that error in the perldoc. According to the limited information I have, error 49 is a bad username or password. I"m trying to figure out if the leading underscore is that culprit because if I do a search for "___________ldapmonitor_test" it works just as well as "ldamonitor_test". I"m wondering If I should ask admin to remove leading underscore or if I'm barking up the wrong tree. I don't think it has anything to do with capath because I can connect and search the tree. The error is authenticating on the bind. -Bryan
