Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Troubleshoot and Support > Support issues and limitations > LDAP repository issues
NameNotFoundException occurs during LDAP repository search
Follow these troubleshooting steps if a javax.naming.NameNotFoundException occurs during a search in an LDAP repository.
Problem
A javax.naming.NameNotFoundException occurs because a root-based search is performed in an LDAP repository, such as Microsoft Active Directory, which does not support root-based search.
To verify the cause of this problem, check the wimconfig.xml file base entry, as shown in the following example:
<config:baseEntries name="dc=ibm,dc=com" nameInRepository=""/>The parameters in this example are mapped to the values specified in the Repository reference settings page of the WAS administrative console.
The name parameter is the virtual member manager base entry of this repository, which must be unique within the virtual member manager realm. When setting up the LDAP repository, the name parameter is mapped to the value specified in the field, Distinguished name of a base entry that uniquely identifies this set of entries in the realm.
The nameInRepository parameter is the LDAP distinguished name of the base entry within the repository. It indicates the starting point for searches in the LDAP directory server. The nameInRepository parameter is mapped to the value specified in the field, Distinguished name of a base entry in this repository.
When setting up the LDAP repository, if the Distinguished name of a base entry in this repository field is left blank, that is nameInRepository="", then the subtree defaults to the root of the LDAP repository, which becomes the starting point for searches. This results in a root-based search. If the repository does not support a root-based search, the JNDI search causes a NameNotFoundException to occur, which in turn causes virtual member manager to throw an exception.
Solution
Set the LDAP server search root when configuring LDAP repositories in virtual member manager.
In the console, on the Repository reference settings page, do not leave the Distinguished name of a base entry in this repository blank, if the LDAP repository does not support root-based searches.
For information about accessing these settings, read about Repository reference settings in the WAS information center.
Related topic
Unable to log in with a valid LDAP repository login ID
Parent topic: LDAP repository issues