Update the federated LDAP user registry on Solaris

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.

Use the helper file...

WP_PROFILE/ConfigEngine/config/helpers/wp_add_federated_xxx.properties

Update the LDAP user registry in the default federated repository

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.

1. Edit wkplc.properties

2. Identify the existing LDAP user registry to update:
   federated.ldap.id
   federated.ldap.host
   federated.ldap.baseDN
   federated.ldap.ldapServerType

3. Under the Federated LDAP repository heading set:
   
   federated.ldap.port
   federated.ldap.bindDN
   federated.ldap.bindPassword

4. Save changes to wkplc.properties.

5. Validate the LDAP server settings...
   ./ConfigEngine.sh validate-federated-ldap -DWasPassword=foo

   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.

6. Update the LDAP user registry in the default federated repository...
   ./ConfigEngine.sh wp-update-federated-ldap -DWasPassword=foo

7. Stop and restart servers, dmgrs, and node agents.

If you 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 Solaris
Related:
Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation