Custom authenticator is never called

• Key: DIRSERVER-365
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Trustin Lee
• Reporter: Giamma

Description

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.

Comments

[Alex Karasulu]

It might be a good idea to get Endi's commentary on this issue.

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

[Trustin Lee]

I checked in the fix. Now it should work as you expected.

[Emmanuel Lecharny]

Closing all issues created in 2005 and before which are marked resolved