Oh the joys of working with AD! :(
Looking at these messages leads me to believe that Peter has the same situation that I have working with our AD. His ldapsearch examples and problems with the null password lead me to believe this. Here is my AD situation. With our AD, you can not CONNECT to it without passing a binddn. So when I try to do the Net::LDAP new command to our AD server it fails, you do not even get a chance to bind to it. There may be a possible solution to the problem but I do not think that Net::LDAP currently handles it. In a ldap URL, you can put in a bindname dn string. Since the Net::LDAP new command can handle ldap URLs, it would be nice if Net::LDAP could handle a url with the bindname parameters too. Due to other pressing work issues I have spent no time researching the possible solutions using Net::LDAP on my AD problem. Regards, Clif Harden Internet: [EMAIL PROTECTED] -----Original Message----- From: Chris Ridd [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 1:18 PM To: Peter Walsham; perl-ldap@perl.org Subject: Re: Blank password bug(?) & work around On 12/1/06 2:24, Peter Walsham <[EMAIL PROTECTED]> wrote: > 3) I cannot use Net::LDAP to authenticate users with empty passwords As Graham and I both noted, you *can* do a bind with a DN and an empty password if you pass noauth => 1 in the bind call. You have to do that instead of passing password => '', which is not what I said earlier - sorry. But I've just tested and verified it does send what you want in the protocol. Cheers, Chris
