+

Search Tips   |   Advanced Search

Configure group attribute definition settings in a federated repository configuration

Because group attribute definition settings apply only to an LDAP repository, we must first configure an LDAP repository. See Manage repositories in a federated repository configuration.


Tasks

  1. In the administrative console, click...

      Security > Global security > User account repository > Available realm definitions > Federated repositories > Configure

    To configure for a specific domain in a multiple security domain environment, click Security domains > domain_name. Under Security Attributes, expand User Realm, and click Customize for this domain. Select the Realm type as Federated repositories and then click Configure.

  2. Under Related items, click Manage repositories.

  3. Click Add > LDAP repository 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 proceeding to the next step.

  4. Under Additional properties, click Group attribute definition.
  5. 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 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 our 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.

  6. Select the scope of the group membership attribute. The default 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.

After completing these steps, group attribute definition settings are configured for our LDAP repository.


What to do next

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

  2. If we are enabling security, complete the remaining steps as specified in Enable WebSphere Application Server security. As the final step, validate this setup by clicking Apply in the Global security panel.
  3. 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.


Subtopics