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 WebSphere Application Server 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>   

Icon that indicates the type of topic Concept topic

Terms and conditions for documentation | Feedback


Timestamp icon Last updated: March 30, 2016 13:35
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=vmm&topic=UnableToGetUserInformationForAGroup
File name: UnableToGetUserInformationForAGroup.html