You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Giamma (JIRA)" <di...@incubator.apache.org> on 2005/07/06 00:26:16 UTC
[jira] Created: (DIREVE-178) Custom authenticator is never called
Custom authenticator is never called
------------------------------------
Key: DIREVE-178
URL: http://issues.apache.org/jira/browse/DIREVE-178
Project: Directory Server
Type: Bug
Components: server main
Versions: 0.9
Reporter: Giamma
Assigned to: Alex Karasulu
I wrote a custom authenticator that will authenticate against our database.
The problem is that it's never called in AuthenticationService.process().
It looks like process() will loop through the configured authenticator, starting with the default one:
for (Iterator i = authenticators.iterator(); i.hasNext(); idx++) {
try {
Authenticator authenticator = (Authenticator) i.next();
// perform the authentication
LdapPrincipal authorizationId = authenticator.authenticate(ctx);
.....
}
}
Unfortunately SimpleAuthenticator will generate a LdapNameNotFoundException exception and process() will just bail out.
Instead it should try the next authenticator.
--
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: (DIREVE-178) Custom authenticator is never called
Posted by "Endi S. Dewata (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-178?page=comments#action_12318506 ]
Endi S. Dewata commented on DIREVE-178:
---------------------------------------
Hi, I can't find the process() method in AuthenticationService. Maybe it's from an older code?
In the current code the work is done in AuthenticationService.authenticate(). The way it works is it will attempt to authenticate using each authenticator. If one fails, it will try the next one until it finds the first authenticator that doesn't throw an exception. If all authenticators fail, the authenticate() method itself will throw an LdapAuthenticationException. Hope this helps.
Endi
> Custom authenticator is never called
> ------------------------------------
>
> Key: DIREVE-178
> URL: http://issues.apache.org/jira/browse/DIREVE-178
> Project: Directory Server
> Type: Bug
> Components: server main
> Versions: 0.9
> Reporter: Giamma
> Assignee: Trustin Lee
>
> I wrote a custom authenticator that will authenticate against our database.
> The problem is that it's never called in AuthenticationService.process().
> It looks like process() will loop through the configured authenticator, starting with the default one:
> for (Iterator i = authenticators.iterator(); i.hasNext(); idx++) {
> try {
> Authenticator authenticator = (Authenticator) i.next();
> // perform the authentication
> LdapPrincipal authorizationId = authenticator.authenticate(ctx);
> .....
> }
> }
> Unfortunately SimpleAuthenticator will generate a LdapNameNotFoundException exception and process() will just bail out.
> Instead it should try the next authenticator.
--
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-365) Custom authenticator is never called
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-365.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> Custom authenticator is never called
> ------------------------------------
>
> Key: DIRSERVER-365
> URL: https://issues.apache.org/jira/browse/DIRSERVER-365
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Giamma
> Assigned To: Trustin Lee
>
> I wrote a custom authenticator that will authenticate against our database.
> The problem is that it's never called in AuthenticationService.process().
> It looks like process() will loop through the configured authenticator, starting with the default one:
> for (Iterator i = authenticators.iterator(); i.hasNext(); idx++) {
> try {
> Authenticator authenticator = (Authenticator) i.next();
> // perform the authentication
> LdapPrincipal authorizationId = authenticator.authenticate(ctx);
> .....
> }
> }
> Unfortunately SimpleAuthenticator will generate a LdapNameNotFoundException exception and process() will just bail out.
> Instead it should try the next authenticator.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIREVE-178) Custom authenticator is never called
Posted by "Trustin Lee (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-178?page=all ]
Trustin Lee resolved DIREVE-178:
--------------------------------
Fix Version: 0.9.2
Resolution: Fixed
I checked in the fix. Now it should work as you expected.
> Custom authenticator is never called
> ------------------------------------
>
> Key: DIREVE-178
> URL: http://issues.apache.org/jira/browse/DIREVE-178
> Project: Directory Server
> Type: Bug
> Components: server main
> Versions: 0.9
> Reporter: Giamma
> Assignee: Trustin Lee
> Fix For: 0.9.2
>
> I wrote a custom authenticator that will authenticate against our database.
> The problem is that it's never called in AuthenticationService.process().
> It looks like process() will loop through the configured authenticator, starting with the default one:
> for (Iterator i = authenticators.iterator(); i.hasNext(); idx++) {
> try {
> Authenticator authenticator = (Authenticator) i.next();
> // perform the authentication
> LdapPrincipal authorizationId = authenticator.authenticate(ctx);
> .....
> }
> }
> Unfortunately SimpleAuthenticator will generate a LdapNameNotFoundException exception and process() will just bail out.
> Instead it should try the next authenticator.
--
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: (DIREVE-178) Custom authenticator is never called
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-178?page=all ]
Alex Karasulu reassigned DIREVE-178:
------------------------------------
Assign To: Trustin Lee (was: Alex Karasulu)
> Custom authenticator is never called
> ------------------------------------
>
> Key: DIREVE-178
> URL: http://issues.apache.org/jira/browse/DIREVE-178
> Project: Directory Server
> Type: Bug
> Components: server main
> Versions: 0.9
> Reporter: Giamma
> Assignee: Trustin Lee
>
> I wrote a custom authenticator that will authenticate against our database.
> The problem is that it's never called in AuthenticationService.process().
> It looks like process() will loop through the configured authenticator, starting with the default one:
> for (Iterator i = authenticators.iterator(); i.hasNext(); idx++) {
> try {
> Authenticator authenticator = (Authenticator) i.next();
> // perform the authentication
> LdapPrincipal authorizationId = authenticator.authenticate(ctx);
> .....
> }
> }
> Unfortunately SimpleAuthenticator will generate a LdapNameNotFoundException exception and process() will just bail out.
> Instead it should try the next authenticator.
--
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: (DIREVE-178) Custom authenticator is never called
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-178?page=comments#action_12318499 ]
Alex Karasulu commented on DIREVE-178:
--------------------------------------
It might be a good idea to get Endi's commentary on this issue.
> Custom authenticator is never called
> ------------------------------------
>
> Key: DIREVE-178
> URL: http://issues.apache.org/jira/browse/DIREVE-178
> Project: Directory Server
> Type: Bug
> Components: server main
> Versions: 0.9
> Reporter: Giamma
> Assignee: Trustin Lee
>
> I wrote a custom authenticator that will authenticate against our database.
> The problem is that it's never called in AuthenticationService.process().
> It looks like process() will loop through the configured authenticator, starting with the default one:
> for (Iterator i = authenticators.iterator(); i.hasNext(); idx++) {
> try {
> Authenticator authenticator = (Authenticator) i.next();
> // perform the authentication
> LdapPrincipal authorizationId = authenticator.authenticate(ctx);
> .....
> }
> }
> Unfortunately SimpleAuthenticator will generate a LdapNameNotFoundException exception and process() will just bail out.
> Instead it should try the next authenticator.
--
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