Re: strange behaviour of SetPassword

[email protected]
Newsgroups gmane.comp.lang.perl.modules.ldap
Message-ID <2100122663.8676871237643809224.JavaMail.root@sz0165a.westchester.pa.mail.comcast.net>

some how I am on your email list, please remove me. 



thanks, 
----- Original Message ----- 
From: "Dieter Kluenter" <[email protected]> 
To: [email protected] 
Sent: Friday, March 20, 2009 2:09:19 PM GMT -05:00 US/Canada Eastern 
Subject: Re: strange behaviour of SetPassword 

Kurt Zeilenga <[email protected]> writes: 

> On Mar 20, 2009, at 7:44 AM, Kurt Zeilenga wrote: 
> 
>> On Mar 20, 2009, at 7:36 AM, Dieter Kluenter wrote: 
>> 
>>> Hi, 
>>> i just test PasswordPolicy and want to modify passwords with 
>>> Net::LDAP::Extension::SetPassword, but when i run this script, 
>>> $msg->gen_password() creats a random password and modifies 
>>> newpassword=> with the radom generated value instead of the defined 
>>> password. Is this a bug or is my script bogus. The docs say 
>>> 
>>> gen_password ( ) 
>>>          Return the password generated in the previous 
>>> "set_password()" 
>>>          call. 
>>> 
>> 
>> My guess is that the documentation is wrong.  The LDAP extended 
>> operation used returns the server generated password.  In your use 
>> of the operation, the server didn't generate a password, so the 
>> generated password field should not be present in the server's 
>> response. 
> 
> That is, the documentation should say something like: 
>         Return the password generated by the server in response to the 
> set_password() call when applicable. 

Kurt, 
thank you. After re-reading RFC-3062 in particular section 3 I 
understood gen_password. It just returnes a server generated random 
password in absence of newpassword. 

-Dieter 

-- 
Dieter Klünter | Systemberatung 
http://www.dpunkt.de/buecher/2104.html 
sip: +49.180.1555.7770535 
GPG Key ID:8EF7B6C6 
53°08'09,95"N 
10°08'02,42"E
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.