Update the federated LDAP user registry on Windows
After creating and using the LDAP user registry in the default federated repository, you may find the LDAP user registry is not working exactly as you would like.For example, we can change the LDAP Bind password.
In a clustered environment, start the dmgr and nodeagent and verify they are able to synchronize.
The update federated LDAP user registry 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 helper file...
WP_PROFILE/ConfigEngine/config/helpers/wp_add_federated_xxx.properties
h3> Update the LDAP user registry in the default federated repository
- Edit wkplc.properties, located in...
WP_PROFILE/ConfigEngine/properties
- Identify the existing LDAP user registry to update:
- Under the Federated LDAP repository heading set:
- Save changes to wkplc.properties.
- Run the ConfigEngine.bat validate-federated-ldap -DWasPassword=foo task to validate the LDAP server settings.
In an environment configured with an LDAP with SSL, during the validation task, you will be prompted to add a signer to the truststore.
For example...
Add signer to the truststore now?
If you do, press y then Enter.
- To update the LDAP user registry in the default federated repository.
cd WP_PROFILE\ConfigEngine
ConfigEngine.bat wp-update-federated-ldap -DWasPassword=foo task
- Stop and restart servers, dmgrs, and node agents.
If created the clustered environment, including the additional nodes, and then completed the steps in this task, run update-jcr-admin on the secondary nodes.
Parent: Update the user registry on Windows
Related:
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation