Unable to login via LDAP to eDiscovery Platform after an upgrade to eDiscovery Platform 8.2
book
Article ID: 100032850
calendar_today
Updated On:
Description
Error Message
[#160005] Authentication failed: User id not found or password was incorrectly typed. Please contact your Clearwell administrator for assistance.
Scenario 1:
For a system where the encrypted LDAP password was previously configured (using
esa.ldap.connectionPassword.enc)
- Login in to eDiscovery Platform as superuser or another System Manager user.
- Go to System > Support Features.
- Choose Property Browser from the dropdown menu and clear the values for esa.ldap.connectionPassword.enc:
- Name of property to change: esa.ldap.connectionPassword.enc
- New value: leave blank
- Check the box for Confirm change
- Click Submit
- Add the clear-text password to the esa.ldap.connectionPassword setting:
- Name of property to change: esa.ldap.connectionPassword
- New value: enter clear-text password
- Check the box for Confirm change
- Click Submit
- Validate with LDAP login to eDiscovery Platform.
Scenario 2:
For a system where the cleartext LDAP password was previously configured
(using
esa.ldap.connectionPassword)
- Login in to eDiscovery Platform as superuser or another System Manager user.
- Go to System > Support Features.
- Add the clear-text password to the esa.ldap.connectionPassword setting:
- Name of property to change: esa.ldap.connectionPassword
- New value: enter clear-text password
- Check the box for Confirm change
- Click Submit
- Validate with LDAP login to eDiscovery Platform
Cause
- As of eDiscovery Platform 8.2, the LDAP authentication password needs to be set through the System Support Features Property Browser, using the esa.ldap.connectionPassword setting. The user will enter a cleartext password that system will encrypt and store.
- The previously used esa.ldap.connectionPassword.enc setting is now ignored. In this scenario, the
esa.ldap.connectionPassword setting will now be entered and encrypted automatically.
Important: LDAP login may fail when both settings are configured.
- Post-upgrade configuration requires the use of Property Browser from System > Support Features as described in the Solutions below.
- To set up a new LDAP configuration, you must use System > Support Features. See Article 000115760
Resolution
**NOTE** Due to LDAP not working, a local account such as the default "superuser" account will need to be used to login to the eDP user interface to perform either of the solutions below.
Issue/Introduction
Unable to login via LDAP to eDiscovery Platform after an upgrade to eDiscovery Platform 8.2.
Was this article helpful?
thumb_up
Yes
thumb_down
No