Enterprise users added to eDiscovery via LDAP have the domain name appended to the username.
Article ID: 100012601
Updated On:
Cause
The LDAP setting "esa.ldap.user.username" is set to read "userprincipalname" instead of "sAMAccountName".
Resolution
Use System > Support Tools > Property Browser to update the LDAP setting "esa.ldap.user.username" to read "sAMAccountName" instead of "userprincipalname".
This will prevent appending the domain name, i.e. @domain.com, at the end of the username during discovery.
To change the ESA configuration settings:
1. Log in to the Clearwell UI as a System Manager user (superuser).
2. Navigate to System > Support Features
3. Choose the support feature "Property Browser" from the pull down list
4. Fill out the fields appropriately
- Name of property to change = esa.ldap.user.username
- New value (leave blank to remove) = sAMAccountName
5. Check "Confirm change. Are you sure?"
6. Click Submit
3. Choose the support feature "Property Browser" from the pull down list
4. Fill out the fields appropriately
- Name of property to change = esa.ldap.user.username
- New value (leave blank to remove) = sAMAccountName
5. Check "Confirm change. Are you sure?"
6. Click Submit
7. Restart eDP services using the CW Utility (option #3 then option #4)
Issue/Introduction
Adding enterprise users to eDiscovery from Active Directory (AD) no longer defaults to just their user ID; it is appending the domain name to the account name, for example:
@domain.com.
If you attempt to edit a user to change permissions or perform any other administrative task on the user, the record cannot be saved. An error pops up asking if you want to convert the user to a local or Enterprise user. If you click to convert the user to Local or Enterprise user, an error pops up stating user has been deleted or does not exist. When a user attempts to log in, a message displays a warning indicating that authentication has failed and that the ID is not found.
Was this article helpful?
Yes
No
Powered by
