Login to Administrative Console using short DN fails with SECJ0369E error in SystemOut.log.
 Technote (troubleshooting)
 
This document applies only to the following language version(s):
English
 
Problem(Abstract)
Login to Administrative Console using short DN fails with SECJ0369E error in SystemOut.log but using fully qualified DN, works.
 
Cause
Same short user DN defined multiple times in LDAP registry in different context. For example:
cn=user1,ou=Users,o=ANYORG
cn=user1,ou=Admin,o=ANYORG
 
Resolving the problem
Following errors logged into SystemOut.log
SECJ0350E: Could not get the uniqueId of the user cn=user1,ou=Users,o=ANYORG.

SECJ0369E: Authentication failed when using LTPA. The exception is Cannot find uniqueID for the user cn=user1,ou=Users,o=ANYORG.

SECJ0222E: An unexpected exception occurred when trying to create a LoginContext. The LoginModule alias is system.WEB_INBOUND and the exception is com.ibm.websphere.security.auth.WSLoginFailedException: Cannot find uniqueID for the user cn=user1,ou=Users,o=ANYORG.

SECJ0118E: Authentication error during authentication for user user1

If multiple users returned during LDAP query, WebSphere can not decide which user to use.

Do not define same user short name multiple times in LDAP registry or use fully qualified DN to logon to Administrative Console.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Security
Operating system(s): Windows
Software version: 6.0.2
Software edition:
Reference #: 1217104
IBM Group: Software Group
Modified date: Sep 15, 2005