directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DIRSERVER-365) Custom authenticator is never called
Date Sat, 21 Apr 2007 11:14:16 GMT

     [ 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.


Mime
View raw message