Federating the LDAP user registry
The stand-alone LDAP user registry configuration is deprecated. Instead, configure the federated LDAP user registry. Run the wp-modify-federated-security task to change to a federated LDAP user registry.
In a stand-alone server environment, you can 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 that they are able to synchronize.
Important
Starting with HCL Digital Experience Version 8.5, the stand-alone LDAP repository is deprecated. Change to the federated LDAP user repository.
Use the wp_security_federated.properties helper file that is in the wp_profile_root/ConfigEngine/config/helpers directory. It ensures that the correct properties are entered. In the following instructions, where the step refers to the wkplc.properties file, use your wp_security_federated.properties helper file.
-
Go to the wp_profile_root/ConfigEngine/properties directory.
-
Open the wkplc.properties file with a text editor.
-
Update the following parameters in the wkplc.properties file under the VMM Federated repository properties heading:
Note
Go to the properties file for specific information about the parameters.
- federated.primaryAdminId - federated.realm - federated.serverId - federated.serverPassword
-
Open a command prompt.
-
Change to the wp_profile_root/ConfigEngine directory.
-
Run the following task to change the configuration to use a federated repository:
- AIX® and Linux™:
./ConfigEngine.sh wp-modify-federated-security -DWasPassword=password -Dskip.ldap.validation=true
- Windows™:
ConfigEngine.bat wp-modify-federated-security -DWasPassword=password -Dskip.ldap.validation=true
- AIX® and Linux™:
-
Important: If you have HCL Portal Version 9.5 or 8.5 with a CF05 or later fix pack applied, then you do not have to complete the following steps.
-
Stop and restart the appropriate servers to propagate the changes. For instructions, go to Starting and stopping servers, deployment managers, and node agents.
-
Log in to HCL Portal as an administrator.
-
Click Administration. Then, click Virtual Portals > Manage Virtual Portals.
-
Edit each Virtual Portal using the pencil icon.
-
Set User realm as blank.
-
Click OK.
-
Edit each Virtual Portal using the pencil icon.
-
Set User realm to match the realm ID that you set for federated.realm.
-
Click OK.
-