authentication failure reasons in IdP logs

[Daniel Fisher]

On Thu, Jun 19, 2014 at 6:09 PM, David Bantz <dabantz at alaska.edu> wrote:
>
> Here’s an example from an apparently resourceful user who after one failure
> tried again providing a different identifier; the two different identifiers
> both correctly result in the same correct dn.
> And in case you’re wondering, yes, both identifiers are correct and both
> were validated by direct inspection of the AD record.
>
> 12:32:23.457 - INFO [edu.vt.middleware.ldap.jaas.JaasAuthenticator:180] -
> Authentication failed for dn:
> CN=jlrosenthal,OU=userAccounts,dc=ua,dc=ad,dc=alaska,dc=edu
> 12:32:23.460 - DEBUG
> [edu.internet2.middleware.shibboleth.idp.authn.provider.UsernamePasswordLoginServlet:176]
> - User authentication for jlrosenthal failed
> javax.security.auth.login.LoginException: Cannot authenticate dn, invalid dn
>

Are you certain those log messages were produced by the same thread?
I'd like to see your login configuration, I'm confused as to what
would produce this behavior.

--Daniel Fisher