[
https://issues.apache.org/jira/browse/DIRSERVER-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Troisi reopened DIRSERVER-782:
--------------------------------------
The described problem seems still present in the ApacheDS 1.0.2 (used with
Jetspeed 2.1.2).
Changing the AuthenticationService.invalidateAuthenticationCaches( LdapDN
principalDn ) call from
authenticator.invalidateCache( getPrincipal().getJndiName() );
to
authenticator.invalidateCache( principalDn );
solve the problem.
> Restart required after changing password
> ----------------------------------------
>
> Key: DIRSERVER-782
> URL: https://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
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: 1.0.1, 1.5.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
