[ https://issues.apache.org/jira/brow...action_12514241 ]

Ersin Er commented on DIRSERVER-1001:
-------------------------------------

I think I can fix this easily if the pb is what I guess. The Authentication 
Service needs a minor fix. I'll handle it tonight.

> Changes to userPassword attribute not reflected by server immediately, if 
performed by another user
> --------------------------------------------------------------------------
-------------------------
>
>                 Key: DIRSERVER-1001
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1001
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>         Environment: * ApacheDS 1.5.1 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> * Windows XP Professional SP2
>            Reporter: Stefan Zoerner
>             Fix For: 1.5.1
>
>         Attachments: changePwd.ldif, tori.ldif
>
>
> Changes to userPassword attribute seem not to be reflected by server immed
iately, if performed by another user. Here is what I did:
> (1) Add this entry to the directory:
> ---
> dn: cn=Tori Amos,dc=example,dc=com
> sn: Amos
> objectClass: person
> objectClass: top
> cn: Tori Amos
> userpassword: secret
> ---
> $ ldapmodify -h localhost -p 10389 -D "uid=admin,ou=system" -w secret -a -
f tori.ldif
> adding new entry cn=Tori Amos,dc=example,dc=com
> (2) Check, that Tori can authenticate
> $ ldapsearch -h localhost -p 10389 -D "cn=Tori Amos,dc=example,dc=com" -w 
secret -b "" -s base "(objectClass=*)" vendorName
> version: 1
> dn:
> vendorName: Apache Software Foundation
> (3) Modify Tori's password
> LDIF-File:
> ---
> dn: cn=Tori Amos,dc=example,dc=com
> changetype: modify
> replace: userPassword
> userPassword: geheim
> -
> ---
> $ ldapmodify -h localhost -p 10389 -D "uid=admin,ou=system" -w secret -f c
hangePwd.ldif
> modifying entry cn=Tori Amos,dc=example,dc=com
> Note, that I use the admin account to perform this operation!
> (4) Check, whether it works
> $ ldapsearch -h localhost -p 10389 -D "cn=Tori Amos,dc=example,dc=com" -w 
geheim -b "" -s base "(objectClass=*)" vendorName
> ldap_simple_bind: Invalid credentials
> ldap_simple_bind: additional info: Bind failed: null
> $ ldapsearch -h localhost -p 10389 -D "cn=Tori Amos,dc=example,dc=com" -w 
secret -b "" -s base "(objectClass=*)" vendorName
> version: 1
> dn:
> vendorName: Apache Software Foundation
> I think this behavior is not correct, because the new password "geheim" should wor
k immediately (as you assume as well). Note that the problem does not occur, if the 
user "Tori Amos" changes her password herself. In this case, the new password is val
id
immediately.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]