+

Search Tips   |   Advanced Search


Deleting the LDAP group member on Windows

If you made changes to your LDAP user registry and no longer require the group member that you created, you can delete the group member from the LDAP user registry.

In a single server environment the WebSphere_Portal and server1 servers can be either stopped or started.

In a clustered environment stop all appservers on the system including WebSphere_Portal and server1 and then start the nodeagent and deployment manager servers before starting the following task.

Perform the following steps to delete the LDAP user registry group member:

  1. Edit...

      profile_root/ConfigEngine/properties/wkplc.properties

  2. Enter a value for the following parameters under the VMM LDAP group member attribute configuration heading:

  3. Save changes to wkplc.properties.

  4. Run...

      ConfigEngine.bat wp-delete-ldap-groupmember -DWasPassword=password task, from the profile_root/ConfigEngine directory, to delete the group member information for your LDAP user registry.

    • Propagate the security changes:

      Option Description
      Standalone cd profile_root/bin
      ./stopServer.sh server1 -username admin_userid -password admin_password
      ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
      ./startServer.sh server1
      ./startServer.sh WebSphere_Portal
      Cluster cd dmgr_profile/bin
      ./stopManager.sh-username admin_userid -password admin_password
      cd profile_root/bin
      ./stopNode.sh -username admin_userid -password admin_password
      ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
      cd dmgr_profile/bin
      ./startManager.sh
      cd profile_root/bin
      ./startNode.sh
      ./startServer.sh WebSphere_Portal

If you performed these steps after creating the clustered environment, run enable-jcr-security on the secondary node.


Parent topic:

Deleting the user registry configurations on Windows


Related tasks


Enable LDAP security after cluster creation