KB483652: Running a report as a user signed in with LDAP authentication configured with Binding instead of Password comparison causes an error to appear when executing a report

Product Manager, Senior • MicroStrategy

This article describes how selecting “Binding” instead of "Password Comparison" for the LDAP Authentication Method, and having the "Use database passthrough authentication to pass the LDAP user credentials to the data warehouse when executing report SQL” setting enabled, can cause a report to fail when executing.

Description

Running a report as a user signed in with LDAP authentication configured with Binding instead of Password comparison causes the following error message appears:
Message not found in user history list. It may have been deleted from other session already. Please refresh your history list.

Steps to Reproduce

Open Strategy Intelligence Server configuration.
Navigate to LDAP > Server.
Select Binding for the LDAP authentication method.

Open the User Editor the desired user.
Navigate to Authentication > Warehouse.
Set the Warehouse Authentication to use Warehouse Passthrough.

Run the report. Notice a variation of the following error appears:
Message not found in user history list. It may have been deleted from other session already. Please refresh your history list.QueryEngine encountered error: Connect failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [HY000:28000: on SQLHANDLE][Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-28000: the account is locked. Error in Process method of Component: QueryEngineServer, Project 'XXX', Job ‘XXX’, Error Code=-2147212544.)"

Why is this happening?

The reason this error appears is because the Binding setting in the LDAP Server configuration causes the user's credentials to be re-authenticated against the LDAP server. As a result, this populates the Warehouse Passthrough.
Since the user's credentials are not the same as the credentials needed to access the database, the report fails to run against the database because the login is not valid.

Solution

To avoid this error, change the LDAP authentication mode to Password comparison and update or clear the credentials in the Warehouse Passthrough.

Open Strategy Intelligence Server configuration.
Navigate to LDAP > Server.
Select Password Comparison for the LDAP authentication method.
Open the User Editor the desired user.
Navigate to Authentication > Warehouse.
Update or clear the Warehouse Passthrough.

Workaround

If a large number of users have been affected, the password can be adjusted using Command Manager by running the script below.
Note: Change

Administrator

to the name of the user.

ALTER USER "Administrator" WHLINK "";

Comment

0 comments

Details

Knowledge Article

Published:

September 24, 2019

Last Updated:

September 24, 2019

Why is this happening?

Solution

To avoid this error, change the LDAP authentication mode to Password comparison and update or clear the credentials in the Warehouse Passthrough.

Open Strategy Intelligence Server configuration.

Navigate to LDAP > Server.

Select Password Comparison for the LDAP authentication method.

Open the User Editor the desired user.

Navigate to Authentication > Warehouse.

Update or clear the Warehouse Passthrough.