Set member attributes in a federated repository configuration
Follow this task to configure member attributes in a federated repository configuration.
Because member attributes apply only to a LDAP repository, first configure an LDAP repository. For more information, see Manage repositories in a federated repository configuration.
- In the admin console, click...
Security | Global security
- 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 we click Add to specify a new external repository, first complete the required fields and click Apply before we can proceed to the next step.
- Under Additional properties, click Group attribute definition.
- Under Additional properties, click Member attributes.
- Click New to specify a new member attribute or Delete to remove a preconfigured member attribute.
- Accept the default, or supply the name of the member attribute in the Name of member attribute field. For example, member and uniqueMember are two commonly used names of member attributes.
The member attribute is used to store the values that reference members that the group contains. For example, a group type with an object class groupOfNames has a member attribute named member; group type with object class groupOfUniqueNames has a member attribute named uniqueMember. An LDAP repository supports multiple group types if multiple member attributes and their associated group object classes are specified.
- Supply the object class of the group that uses this member attribute in the Object class field. If this field is not defined, this member attribute applies to all group object classes.
- Select the scope of the member attribute. The default value is Direct.
- The member attribute contains direct members only. Direct members are members that are directly contained by the group. For example, if Group1 contains Group2 and Group2 contains User1, then User1 is a direct member of Group2, but User1 is not a direct member of Group1.
- The member attribute contains both direct members and nested members.
- The member attribute contains direct members, nested members, and dynamic members.
ResultsAfter completing these steps, member attributes are configured for your LDAP repository.
- After configuring the federated repositories, click Security > Global security to return to the Global security 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 Global security panel. If Federated repositories is not identified in the Current realm definition field, the federated repositories configuration is not used by WAS.
- If enabling security, complete the remaining steps as specified in Enable security for the realm. As the final step, validate this setup by clicking Apply in the Global security panel.
- Save, stop, and restart all WAS servers (dmgrs, nodes, and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.
Member attributes collection
Member attributes settings