Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <15243329.1163776841648.JavaMail.jira@brutus>
Date: Fri, 17 Nov 2006 07:20:41 -0800 (PST)
From: "Ate Douma (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-782) Restart required after changing
 password
In-Reply-To: <20503558.1163774499960.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DIRSERVER-782?page=comments#action_12450765 ] 
            
Ate Douma commented on DIRSERVER-782:
-------------------------------------

Right...
Well, we probably will drop the ApacheDS "embedded" feature from Jetspeed-2 and have the users run it themselves.
Ok, that would be great, thanks.

BTW: are you going to provide "normal" src and binary distributions too, besides now only binary setup dists?
I also thought that to be a requirement for ASF releases...

For development, I honestly don't need nor like to be forced to *install* ADS.

Regards,

Ate


> Restart required after changing password
> ----------------------------------------
>
>                 Key: DIRSERVER-782
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-782
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0
>         Environment: Ubuntu 6.06, Java 1.5, Jetspeed-2.1-dev
>            Reporter: Ate Douma
>            Priority: Blocker
>
> AuthenticationService.invalidateAuthenticationCaches( LdapDN principalDn ) calls:
>   authenticator.invalidateCache( getPrincipal().getJndiName() );
> instead of (what I think it should do):
>    authenticator.invalidateCache( principalDn );
> This results in original credentials remaining in the Authenticator cache, blocking a user to login again after changing the credentials.
> I'm trying to upgrade our Jetspeed-2 codebase to use the new ApacheDS 1.0.0 but this is a blocker right now.
> (NB: another one is that we still build with maven-1..., I can't find any docs how to embed ApacheDS using maven-1, or -2 for that matter)
> When I modified the AuthenticationService the way I think it should, the problem is solved.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira