This exception occurs when you don’t use the same user DN in the Java code as is stored in LDAP and in the LiveCycle database.

For example, the myuniqueID in the EDCPRINCIPALENTITY table is:

myuniqueid=XXXXXXXX,ou=People,dc=company,dc=com

and in the Java code it’s:

myuniqueid=XXXXXXXX,ou=people,dc=company,dc=com

The ou has a capital “P” in LDAP and in the DB, but in the Java code, it was attempting to find the user with a lowercase “p” for the ou. This error can occur in LiveCycle ES as Adobe changed the LDAP synchronization algorithm to canonicalize the DN strings during synchronization. As a result, the DN strings appear in the DB exactly as they are defined in LDAP (including case-sensitivity).

Solution

Make sure that you are using exactly the same user DN in the Java code as it is stored in LDAP and in the LiveCycle database.

reference: (181473688)

VN:F [1.9.22_1171]

Was this helpful? Please rate the content.

please wait...

Rating: 9.0/10 (1 vote cast)

LiveCycle ES: AuthenticationManagerImpl errorCode:16386 errorCodeHEX:0x4002, 9.0 out of 10 based on 1 rating