ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
LDAP user cannot log into UI after name changed in Active Directory
Article ID: 87735
CA Automic Workload Automation - Automation Engine
Error Message : N/A
LDAP user cannot log into the User Interface (UI) after name changed in Active Directory.
Cause type: Configuration Root Cause: Active Directory doesn't force an update that can be picked up by the LDAP mechanism used by AE to connect to LDAP.
OS Version: N/A
This behavior is a result of Active Directory (AD) not forcing an update that will be picked up by the LDAP mechanism used by the Automation Engine (AE) to connect to LDAP. To resolve this issue, the user that changed their name in Active Directory must also force a password change in AD along with the LDAP sync by following these steps:
Log into your computer and change your password manually through Windows.
Login to AE and mark the LDAP flag and save the account.
Next, try to login to AE again with the updated LDAP name and new password.
If that does not work, then have your Windows admin force a password change in Active Directory by resetting the password.