Hello Emmanuel, thanks for the reply. I am going to check the links you gave me.
I use JXplorer to browse the APACHE DS and I noticed something that I am not able to explain myself, those are the steps: - I connect with my user, then I remove the userPassword attribute and submit it (so the userPassword attribute exists with a blank value). - I change the password and disconnect. - Now, I connect again with the new password and it works! Can u tell me why seems that JXplorer can remove the principal/credentials from the authenticationCache without a LDAPServer restart? Might it be that it is a simple error on my code and not related to any bug? Flavio ________________________________________ Da: Emmanuel Lecharny [mailto:[EMAIL PROTECTED] Inviato: venerdì 16 marzo 2007 11.10 A: Apache Directory Developers List Oggetto: Re: [ApacheDS] Password refresh Hi Flavion I reply on the dev list, because I think it's much more a dev related issue than an user one... We have fixed this issue and it will be released in the 1.0.2 version, coming very soon. In the meantime, you can check out the latest version from the svn repository, or downloaded the nighty build here : http://iktek.com/index.jsp?rubrique=ads The cache is now updated when a user change a password (I least, I hope it works :) Emmanuel On 3/16/07, Flavio Minori <[EMAIL PROTECTED]> wrote: Hi all, I am devoloping my own application and I use Apache DS 1.0.1 + Spring + Acegi. When I need to update the userPassword attribute, I use something like this: [CODE] ... BasicAttribute userPasswordAttribute = new BasicAttribute("userPassword"); ModificationItem replacedPassword = new ModificationItem(DirContext.REPLACE_ATTRIBUTE,userPasswordAttribute); ModificationItem[] modificationItemArray = new ModificationItem[1]; modificationItemArray[0] = "newPasswordString"; try { ldapTemplate.modifyAttributes(distinguishedName.toString(),modificationItemA rray); } catch (DataAccessException e) { ... [/CODE] This works right, but I need to restart APACHE DS to make the changes happens. This is due to APACHEDS which uses a cache for the simple authenticator. Possible solutions for me are: 1) invalidate this cache from the server.xml configuration? How can I do? 2) use my own authenticator that extends the SimpleAuthenticator .. just remove 2 lines about cache check .. but I need to rebuild ApacheDS completely. Best regards, Flavio -- Cordialement, Emmanuel Lécharny www.iktek.com
