Configure the federated LDAP user registry
The stand-alone LDAP user registry configuration is deprecated. Instead, configure the federated LDAP user registry. If we are migrating from WebSphere Portal v7.0 or 8.0 with a stand-alone LDAP user registry, we can continue to use the stand-alone LDAP user registry. However, we should run the wp-modify-federated-security to change to a federated LDAP user registry. In a stand-alone server environment, complete the following task when the servers are either stopped or started. In a clustered environment, start the deployment manager and node agent. Then, verify they are able to synchronize.
Starting with IBM WebSphere Portal v8.5, the stand-alone LDAP repository is deprecated. Change to the federated LDAP user repository. Use the wp_security_federated.properties helper file in the WP_PROFILE/ConfigEngine/config/helpers directory. It ensures the correct properties are entered. In the following instructions, where the step refers to wkplc.properties, use the wp_security_federated.properties helper file.
- cd WP_PROFILE/ConfigEngine/properties
- Edit wkplc.properties
- Update the following parameters in wkplc.properties under the VMM Federated repository properties heading:
- federated.primaryAdminId
- federated.realm
- federated.serverId
- federated.serverPassword
- Open a command prompt.
- Change the configuration to use a federated repository:
- cd WP_PROFILE/ConfigEngine.
./ConfigEngine.sh wp-modify-federated-security -DWasPassword=foo -Dskip.ldap.validation=true
- Stop and restart the appropriate servers to propagate the changes.
Parent Administrative tasks