KB46551: If a user's LDAP password changes, the warehouse credentials are not updated unless an LDAP authentication is done in MicroStrategy 9.x and 10.x

SYMPTOM:
 
When using LDAP credentials for warehouse pass-through and Windows Authentication to log in to Strategy, if a user's LDAP password changes, the warehouse credentials are not updated unless an LDAP authentication is done in Strategy 9.x and 10.x. 
 
CAUSE:
 
This is working as designed. LDAP pass-through was designed to be used in conjunction with LDAP authentication. Consider the following facts regarding the aforementioned Strategy authentication methods.

1. When using NT Authentication (Windows Authentication), Strategy matches the Windows user's SID to an existing metadata user's SID. This match is then used to allow that specific user to log in as the corresponding metadata user.
2. When using LDAP Authentication, Strategy performs a search of the specific user on the LDAP Server by the username input and then performs a password compare between the password input and the password stored on the LDAP Server. A password is never stored in the metadata during the LDAP Authentication.

When using LDAP credentials for warehouse pass-through, the credentials must be stored in the metadata in order to pass them each time it is required to query the database for that user. If Windows authentication is in use, Strategy does not have a way to know if the LDAP credentials have been changed or updated. Therefore, it is necessary to perform at least one LDAP login following the LDAP password change in order to update the password credentials in the metadata.
 
ACTION / WORKAROUND:
 
Every time an LDAP user changes their password, an LDAP authentication log-in must be done in order to correctly update the LDAP credentials for LDAP warehouse pass-through. Setting up LDAP as a secondary log-in option is suggested so that users can perform this step following the password change.