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
Unable to get members for a group in federated repositories
Follow the steps listed here to troubleshoot when you are unable to get members of the respective group in federated repositories.
Problem
You are unable to get members of the respective group in federated repositories. The members are not shown when checking group members even though you are able to access the groups for the same user using the WAS administrative console (Users and Groups > Manager Users). Also, the trace does not display any obvious exception for this problem.
This problem occurs because in the wimconfig.xml file both memberAttributes and membershipAttribute are configured with the same name, as shown in the following example:
<config:groupConfiguration> <config:memberAttributes name="uniquemember" objectClass="groupOfUniqueNames" scope="direct"/> <config:membershipAttribute name="uniquemember" scope="direct"/> </config:groupConfiguration>
Solution
Remove the membershipAttribute configuration from the wimconfig.xml file, because the attribute uniquemember is a member attribute in the LDAP repository, but it is not a membershipAttribute.
The corrected configuration for the example described in the previous section is shown here:
<config:groupConfiguration> <config:memberAttributes name="uniquemember" objectClass="groupOfUniqueNames" scope="direct"/> </config:groupConfiguration>
Related topics
Member and membership attribute configuration
Parent topic: Groups and membership issues and limitations