[ http://issues.apache.org/jira/brows...245
0768 ]

Ate Douma commented on DIRSERVER-782:
-------------------------------------

The weirdest thing:
I just replied *by mail* to the comment from Emmanuel, with 2 inline comment
s.
But somehow my mail was scanned and my comments extracted as new comment for
 this issue..., without context of course.
I certainly won't do that again 

Anyway, because my previous comment is somewhat incomprehensible now, I'm pr
oviding it again below, not *with* context:

> I guess you *must* use the ADS jars, because of maven 1/maven 2 incompatibility ..
.
Right...
Well, we probably will drop the ApacheDS "embedded" feature from  Jetspeed-2
 and have the users run it themselves.

>
> We will try to get a 1.0.1 out soon, and we also check to see if your modification
 can be applied right away.
Ok, that would be great, thanks.

BTW: are you going to provide "normal" src and binary distributions too, bes
ides 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* AD
S.



> 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 i
s solved.

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

[ Post a follow-up to this message ]