adAuthenticator BAD_NAME but Login Success

[Raymond Gardner]

Hi Nate,

I've experienced this too.  I'm a newbie but I think I can explain.

I believe after authentication, the ldaptive libraries attempt a 2nd request for attribute resolution.  I believe this 2nd request throws this InvalidNameException because your {user} does not have search capabilities with your AD server.

> 2016-07-29 11:23:52,923 - DEBUG [org.ldaptive.provider.jndi.NamingExceptionUtils:358] - naming exception class javax.naming.InvalidNameException is ambiguous, maps to multiple result codes: [INVALID_DN_SYNTAX, NAMING_VIOLATION]
> 2016-07-29 11:23:52,928 - DEBUG [org.ldaptive.auth.Authenticator:381] - entry resolution failed for resolver=[org.ldaptive.auth.SearchEntryResolver at 1632642271::factory=null, baseDn=, userFilter=null, userFilterParameters=null, allowMultipleEntries=false, subtreeSearch=false, derefAliases=null, followReferrals=false, searchEntryHandlers=null]
> org.ldaptive.LdapException: javax.naming.InvalidNameException: helloworld at campus.csu.edu: [LDAP: error code 34 - 0000208F: NameErr: DSID-03100200, problem 2006 (BAD_NAME), data 8350, best match of:
	'helloworld at campus.csu.edu'

I concede the possibility of being wrong with my assumption, however.

****************************************************************
This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. NTT America makes no warranty that this email is error or virus free. Thank you.
****************************************************************