directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flavio Minori" <>
Subject R: [ApacheDS] Password refresh
Date Fri, 16 Mar 2007 10:36:38 GMT
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
- 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?



Da: Emmanuel Lecharny [] 
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 :

The cache is now updated when a user change a password (I least, I hope it
works :)

On 3/16/07, Flavio Minori <> wrote:
Hi all,
I am devoloping my own application and I use Apache DS 1.0.1 + Spring +
When I need to update the userPassword attribute, I use something like this:

BasicAttribute userPasswordAttribute = new BasicAttribute("userPassword"); 
ModificationItem replacedPassword = new
ModificationItem[] modificationItemArray = new ModificationItem[1];
modificationItemArray[0] = "newPasswordString"; try { 
} catch (DataAccessException e) { ...

This works right, but I need to restart APACHE DS to make the changes
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

Best regards,


Emmanuel LĂ©charny 

View raw message