vIDM directory port reverts to old port from 636 after updating the configuration.
search cancel

vIDM directory port reverts to old port from 636 after updating the configuration.

book

Article ID: 433771

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • After updating an LDAPS directory configuration, the new port number reverts to previous port.
  • Test connections to the newly configured port are sucsessful.
  • The 'config-state-json' file is corrupt;
    • /usr/local/horizon/conf/states/<TENANT_NAME>/<WORKER_ID>/

Environment

VMware Identity Manager 3.3.7

Cause

This issue occurs when the config-state.json file becomes corrupted, preventing configuration changes from being retained. This corruption can be compounded if the directory was originally configured using the standard "LDAP" directory type instead of the required "Active Directory over LDAP" type.

Resolution

To resolve this issue, you must recreate the directory connection to clear the corrupted state.

  1. Navigate to the Directory administration page in VMware Identity Manager.

  2. Delete the existing directory configuration.

  3. Follow the steps in the document bellow, focusing on the AD over LDAP section.

Additional Information

Deleting the directory and reconfiguring will rebuild the 'config-state-json' and therefore resolve the corruption.