Update the stand-alone LDAP user registry on HP-UX

 

+

Search Tips   |   Advanced Search

 

After configuring and using the standalone LDAP user registry, you may find that your LDAP user registry is not working exactly as you would like. You can easily update the LDAP user registry and make the necessary changes. For example, you can change your LDAP Bind password. Ensure that the server1 and WebSphere_Portal servers are stopped before starting this task.

Perform the following steps to update the stand-alone LDAP user registry:

The wp-update-standalone-ldap task does not modify the administrative users, the entity types, the LDAP entity types, the LDAP group membership attributes, the LDAP group configuration, or the LDAP context pool. See the separate tasks for updating these parameters.

Use the wp_security_xxx.properties helper file, located in the WP_PROFILE/ConfigEngine/config/helpers directory, when performing this task to ensure the correct properties are entered; see Configuration task properties for information about using the helper file. In the instructions below, when the step refers to the wkplc.properties file, you will use your wp_security_xxx.properties helper file.

  1. Use a text editor to open the wkplc.properties file, located in the WP_PROFILE/ConfigEngine/properties directory.
  2. Enter the following parameter in the wkplc.properties file under the Stand-alone LDAP repository heading to identify the stand-alone LDAP user registry that you want to update:
  3. Update the following required parameters in the wkplc.properties file under the Stand-alone LDAP repository heading:

    See the wkplc.properties file for specific information about the required parameters and for advanced parameters.

  4. Save your changes to the wkplc.properties file.
  5. Run the ./ConfigEngine.sh validate-standalone-ldap -DWasPassword=password task to validate your LDAP server settings.
  6. To update the stand-alone LDAP user registry:
    1. Run the ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password task from the WP_PROFILE/bin directory.
    2. Run the ./ConfigEngine.sh wp-update-standalone-ldap -DWasPassword=password task, from the WP_PROFILE/ConfigEngine directory.
  7. Choose one of the following options to propagate the security changes:
    Option Description
    Standalone environment Run the following tasks to propagate the security changes in a standalone environment:
    1. ./stopServer.sh server1 -username admin_userid -password admin_password, from the WP_PROFILE/bin directory
    2. ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password, from the WP_PROFILE/bin directory
    3. ./startServer.sh server1, from the WP_PROFILE/bin directory
    4. ./startServer.sh WebSphere_Portal, from the WP_PROFILE/bin directory
    Clustered environment Run the following tasks to propagate the security changes in a clustered environment:
    1. ./stopManager.sh, from the dmgr_profile_root\bin directory
    2. ./stopNode.sh -username admin_userid -password admin_password, from the WP_PROFILE/bin directory
    3. ./stopServer.sh server1 -username admin_userid -password admin_password, from the WP_PROFILE/bin directory
    4. ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password, from the WP_PROFILE/bin directory
    5. ./startManager.sh, from the dmgr_profile_root\bin directory
    6. ./startNode.sh, from the WP_PROFILE/bin directory
    7. ./startServer.sh server1, from the WP_PROFILE/bin directory
    8. ./startServer.sh WebSphere_Portal, from the WP_PROFILE/bin directory

 

Parent topic

Updating your user registry on an HP-UX