You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2006/11/17 15:41:39 UTC
[jira] Created: (DIRSERVER-782) Restart required after changing
password
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
Re: [jira] Commented: (DIRSERVER-782) Restart required after changing password
Posted by Emmanuel Lecharny <el...@gmail.com>.
Obviously, embedding ADS is the best solution for you. I do think that it
should be something easy, and you may not need to use maven for that, just
the jars.
I don't know if you have read the following materials :
http://docs.safehaus.org/display/APACHEDS/Embedding+ApacheDS. I don't know
either if this is good enough for you tu embed ADS. I guess that the ADS
wiki *should* be updated for users like you. (man, the current doco sucks so
much ...)
Regarding src jars, the answer is : yes. The question is : when ? :(
Emmanuel
On 11/17/06, Ate Douma (JIRA) <ji...@apache.org> wrote:
>
> [
> 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
>
>
>
--
Cordialement,
Emmanuel Lécharny
[jira] Updated: (DIRSERVER-782) Restart required after changing
password
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-782:
----------------------------------------
Fix Version/s: 1.5.0
1.0.1
We need to investigate the implication of such a fix in the server.
Let's mark it as to be fixed for 1.0.1 and 1.5.0
> 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
> 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.
[jira] Commented: (DIRSERVER-782) Restart required after changing
password
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-782?page=comments#action_12455177 ]
Alex Karasulu commented on DIRSERVER-782:
-----------------------------------------
Ate,
Having normal tar/zip balls is not an Apache release requirement. However it's a good thing to have. How about helping out over here to rig that into our build.
Thanks.
> 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
[jira] Closed: (DIRSERVER-782) Restart required after changing
password
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-782.
-----------------------------------
Resolution: Fixed
The following tests confirm that updates are correctly handled to invalidate the credential cache:
o test11InvalidateCredentialCache
o testDIRSERVER782
I just added the last test but both test cases test to make sure the cache is properly invalidated. Please confirm this bug no longer exists and if so I will open this JIRA issue again.
Thanks!
> 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
> Assigned To: 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.
[jira] Reopened: (DIRSERVER-782) Restart required after changing
password
Posted by "Alberto Troisi (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSERVER-782) Restart required after changing
password
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (DIRSERVER-782) Restart required after changing
password
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-782?page=comments#action_12450754 ]
Emmanuel Lecharny commented on DIRSERVER-782:
---------------------------------------------
I guess you *must* use the ADS jars, because of maven 1/maven 2 incompatibility ...
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.
> 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
[jira] Assigned: (DIRSERVER-782) Restart required after changing
password
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-782:
---------------------------------------
Assignee: Alex Karasulu
> 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
> Assigned To: 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.
[jira] Commented: (DIRSERVER-782) Restart required after changing
password
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-782?page=comments#action_12450768 ]
Ate Douma commented on DIRSERVER-782:
-------------------------------------
The weirdest thing:
I just replied *by mail* to the comment from Emmanuel, with 2 inline comments.
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 providing 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, 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.
> 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
[jira] Closed: (DIRSERVER-782) Restart required after changing
password
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-782.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.0.1)
(was: 1.5.0)
1.5.2
Recent changes in BigBang have fixed this issue.
> 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.5.2
>
>
> 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.