
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Ubuntu 6.06, Java 1.5, Jetspeed-2.1-dev
|
|
| Resolution Date: |
27/Mar/08 04:18 PM
|
|
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.
|
|
Description
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|