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 > Groups and membership issues and limitations
No results returned when searching groups in LDAP repository
Follow the steps listed here to troubleshoot when searching for groups in an LDAP repository does not return any results.
Problem
Search for groups in an LDAP repository does not return any results. However, there is no exception reported in the virtual member manager trace. Also, the same search performed in a file repository returns the expected results.
This problem occurs because the objectClass and relative distinguished name (RDN) configuration do not match.
For example, the following sample search filter shows objectClass=groupofnames and cn=TD*:
0000001b LdapConnectio > com.ibm.ws.wim.adapter.ldap.LdapConnection JNDI_CALL search(String, String, Object[], SearchControls) ENTRY dc=pdm (&(objectClass=groupofnames)(cn=TD*)) null [searchScope: 2, timeLimit: 600000, countLimit: 0, returningObjFlag: true, returningAttributes: [objectClass, ibm-entryuuid, description, cn]]However, the LDAP search result for any group starting with “TD” shows objectClass=groupofuniquenames, and hence does not return any results.
The cause of this problem is because objectClass is configured as groupofnames in the wimconfig.xml file as shown here:
<config:ldapEntityTypes name="Group"> <config:objectClasses>groupofnames </config:objectClasses> </config:ldapEntityTypes>
Solution
Correct the configuration of objectClass of the group in the wimconfig.xml file.
The corrected configuration for the example described in the previous section is shown here:
<config:ldapEntityTypes name="Group"> <config:objectClasses>groupofuniquenames </config:objectClasses> </config:ldapEntityTypes>
Parent topic: Groups and membership issues and limitations