[ 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
