Configure group attribute definition settings in a federated repository configuration
Follow this task to configure group definition settings in a federated repository configuration. Because group attribute definition settings apply only to a Lightweight Directory Access Protocol (LDAP) repository, first configure an LDAP repository. For more information, see Manage repositories in a federated repository configuration.
Procedure
- In the console, click Security > Secure administration, applications, and infrastructure.
- Under User account repository, select Federated repositories from the Available realm definitions field and click Configure.
- Under Related items, click Manage repositories.
- Click Add to specify a new external repository or select an external repository that is preconfigured.
If you click Add to specify a new external repository, first complete the required fields and click Apply before you can proceed to the next step.
- Under Additional properties, click Group attribute definition.
- Supply the name of the group membership attribute in the Name of group membership attribute field. Only one membership attribute can be defined for each LDAP repository.
Every LDAP entry should have this attribute to indicate the groups to which this entry belongs. For example, memberOf is the name of the membership attribute that is used in Active Directory. The group membership attribute contains values that reference groups to which this entry belongs. If UserA belongs to GroupA, then the value of the memberOf attribute of UserA should contain the distinguished name of GroupA.
If your LDAP server does not support the group membership attribute, then do not specify this attribute. The LDAP repository can look up groups by searching the group member attributes, though the performance might be slower.
- Select the scope of the group membership attribute. The default value is Direct.
- Direct
- The membership attribute contains direct groups only. Direct groups are the groups that contain the member. For example, if Group1 contains Group2 and Group2 contains User1, then Group2 is a direct group of User1, but Group1 is not a direct group of User1.
- Nested
- The membership attribute contains both direct groups and nested groups.
- All
- The membership attribute contains direct groups, nested groups, and dynamic members.
Results
After completing these steps, group attribute definition settings are configured for your LDAP repository.
What to do next
- After configuring the federated repositories, click Security > Secure administration, applications, and infrastructure to return to the Secure administration, applications, and infrastructure panel. Verify that Federated repositories is identified in the Current realm definition field. If Federated repositories is not identified, select Federated repositories from the Available realm definitions field and click Set as current. To verify the federated repositories configuration, click Apply on the Secure administration, applications, and infrastructure panel. If Federated repositories is not identified in the Current realm definition field, your federated repositories configuration is not used by WebSphere Application Server.
- If you are enabling security, complete the remaining steps as specified in Enabling security for the realm. As the final step, validate this setup by clicking Apply in the Secure administration, applications, and infrastructure panel.
- Save, stop, and restart all the product servers (deployment managers, nodes, and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.
Group attribute definition settings