Standalone server: Configure Portal to use dynamic groups on z/OS

By default, WebSphere Portal is enabled for static groups. However, the Virtual Member Manager (VMM) allows users to be members of either static or dynamic groups. Static groups are those where a persistent binding exists between a group and its members. Dynamic groups are those where a search query is defined to retrieve the members of a group. If you have the LDAP server configured to use dynamic groups, complete the steps in this task for WebSphere Portal to use dynamic group queries when you setup the LDAP server.

Perform the required tasks to configure either a stand-alone or federated LDAPserver security.

The steps in this task use groupOfURLs as the object class for dynamic groups and memberURL as the dynamic membership attribute. The actual values for object classes and dynamic membership attributes can vary depending on the LDAP server. For this reason, you should export an LDIF file to verify the object classes and dynamic membership attributes.

Clustered environments: Perform the following steps on the dmgr then synchronize the nodes.

Configure WebSphere Portal to use dynamic groups

1. If we are using a Standalone LDAP server...

   1. cd WP_PROFILE/cells/cell_name/wim/config

   2. Edit wimconfig.xml

   3. Add the following line to the <config:groupConfiguration> tag:

      <config:dynamicMemberAttributes name="memberurl" objectClass="groupofurls"/>
      

   4. Save and close wimconfig.xml.

2. If we are using a Federated LDAP server...

   1. Log in to the WAS admin console.

   2. Select Security > Global security.

   3. In Available realm definitions, select Federated repositories and click Configure.

   4. In Related Items, click Manage repositories.

   5. Select the appropriate repository from the list.

   6. In Additional Properties, click Group attribute definition then click Dynamic member attributes.

   7. Click New and specify values for the Name and Object class fields as appropriate.

      For example,

      • Name: memberurl

      • Object class: groupofurls

   8. Click OK and save the changes to the master configuration.

3. Stop and restart servers, dmgrs, and node agents.

Parent: Standalone server: Configure Portal to use a user registry