Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository


Configure dynamic member attributes in a federated repository configuration

Follow this task to configure dynamic member attributes in a federated repository. Because dynamic member attributes apply only to a Lightweight Directory Access Protocol (LDAP) repository, first configure an LDAP repository. See Manage repositories in a federated repository.

A dynamic group defines its members differently than a static group. Instead of listing the members individually, the dynamic group defines its members using an LDAP search. The filter for the search is defined in a dynamic member attribute. For example, the dynamic group uses the structural objectclass groupOfURLs, or auxiliary objectclass ibm-dynamicGroup, and the attribute memberURL, to define the search using a simplified LDAP URL syntax:

ldap:/// <base DN of search> ? ? <scope of search> ? <searchfilter>

The following is an example of the LDAP URL that defines all entries that are under o=Acme with the objectclass=person:

ldap:///o=Acme,c=US??sub?objectclass=person

If both member and dynamic member attributes are specified for the same group type, this group type is a hybrid group with both static and dynamic members.


Procedure

  1. In the admin console, click Security > Global security.
  2. Under User account repository, select Federated repositories from the Available realm definitions field and click 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.

  3. Under Related items, click Manage repositories.
  4. Click Add > LDAP repository 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.

  5. Under Additional Properties, click LDAP entity types.

  6. Click the link for Group entity type.

  7. In the Object Classes field, add the entry for the object class, for example, groupOfUrls. Delimit multiple entries with a semicolon (;).

  8. Click OK.

  9. Under Additional properties, click Group attribute definition.

  10. Under Additional properties, click Dynamic member attributes.

  11. Click New to specify a new dynamic member attribute or Delete to remove a preconfigured dynamic member attribute.

  12. Specify the name of the dynamic member attribute in the Name of dynamic member attribute field. The name of the dynamic member attribute defines the filter for dynamic group members in LDAP, for example, memberURL is the name of a commonly used dynamic member attribute.

  13. Specify the object class of the group that contains the dynamic member attribute in the Dynamic object class field, for example, groupOfURLs. If this property is not defined, the dynamic member attribute applies to all group object classes.
  14. Save the configuration changes in the administration console: Click System administration > Save changes to master repository > Save.

  15. This next step involves using a wsadmin command and cannot be done through the admin console. Start the wsadmin scripting tool and connect to a server, by using the following command: 
    wsadmin –username username –password password

  16. Use the addIdMgrPropertyToEntityTypes command to add the dynamic member attribute specified in step 12 to the federated repositories schema. The dynamic member attribute needs to be added to the entity type Group in the federated repositories schema otherwise an error occurs while creating a group in an LDAP repository configured under federated repositories using the create() API and specifying the memberURL attribute and its value. The correctness of the value of the memberURL attribute is not validated because LDAP does not validate this.

    In the following example, the memberURL property is added to the entity type Group: 

    $AdminTask addIdMgrPropertyToEntityTypes {-name memberURL -dataType String -entityTypeNames Group -repositoryIds repository_ID}

  17. Save the configuration changes. 
    $AdminConfig save


Results

After completing these steps, dynamic member attributes are configured forthe 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, your federated repositories configuration is not used by WAS.

  2. If you are 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.

  3. Save, stop, and restart all the product 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.


Related


Dynamic member attributes collection
Dynamic member attributes settings

+

Search Tips   |   Advanced Search