Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Micro Focus Contributor
Micro Focus Contributor

LDAP Binder user causes DAS issues when normal domain user

I have come across a issue when Incorrect capabilities for the LDAP Binder user may cause  DAS sync issues.


The LDAP Binder user needs to have "read access to all users objects".  This usually means they must be a member of Domain Admins in AD.  If they are not, then new users will be add to the IAP, but deletions from AD will not be propagated to the IAP.


In this case we need to check if binder user for LDAP connection has sufficient rights.


Check in Active Directory, look up the Binder user, open the Properties and select the "Member Of" tab, and correct to right membership. This should help


Tags (1)
1 Reply
Visitor.. Stefan Sauerlae

Re: LDAP Binder user causes DAS issues when normal domain user

Hi, its possible to connect to AD using ldp.exe (see http://technet.microsoft.com/en-us/library/cc794810(WS.10).aspx) and use the same bind user as in LDAP connection setting for a DAS job.

This way you can verify if the bind user is able to connect and see the AD objects.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.