Re: perl, adsi, ADAM, and AD

I have been doing some stuff with Active Directory and LDAP with perl, and ever had problems to get the stuff right. Seems that binding to a global catalog and port 3268 is more reliable than the default LDAP port (389). Then, binding with a full DN sometimes worked, sometimes didn't; surprisingly binding with userPrincipalName (user@example.com) worked as well as binding with sAMAccountName without any further qualifier; the base DN must be right, however (and the password, of course.)

The error you get sounds like either wrong base DN / search scope or wrong authentication mechanism. Tried kerberos?

On which platform are you working? If you happen to work on some UNIX flavour with OpenLDAP installed, you might do a simple bind with ldapsearch, monitor the traffic with ethereal and compare the chatting to what perl produces.

I have to do some updates to my code in an AD/perl environment the next days, I'll update this comment once I got soaked with that stuff again... meanwhile, good luck with my feeble advice ;-)

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: perl, adsi, ADAM, and AD