LDAP Import fails if you use a CN other than Users..
Issue Description:
When we import users through LDAP, it seems like if we use the CN = Users as a Base DN its working fine.
If you use any other CN apart from that its showing error message like "FAILURE : Error occurred while trying to connect with LDAP Server - Please check your inputs."
Solution:
In Base DN instead of CN please use OU as given below.
OU=Test OU,DC=domainname,DC=com
New to ADSelfService Plus?
Related Articles
Query to find out the users who are updated through LDAP import (MSSQL & PGSQL)
This should be handy during Audit. Execute the queries under Reports->New Query Report select ch.ciid "CI ID", ci.ciname "CI Name", chd.attribute "Attribute", chd.newvalue "New Value", chd.oldvalue "Old Value", ch.editmode "Edit Mode", ...Sample search filter used to import requesters based upon group membership
Sample search filter used to import requestors based upon group membership only (i.e. not just import all users under a specific OU). (&(objectCategory=test)(sAMAccountName=*)(memberOf:test group=CN=test ...User Import Issue (CSV)
While importing Contact or Support Rep via CSV many customer face issue with importing getting failed The most comman reason is that the CSV file may not have the password for the users getting imported We have set the Display Name and Login Name as ...How to import users from AD under a site value configured in different attributes of AD
Applicable for build - 14306 and above. SDP MSP uses attribute values while importing from AD. By Default , the officesite name in AD config is mapped to SDP MSP Site field. In case users wants to use different field for the same purpose, use its ...Duplicate users while importing from AD
Use the below queries; To find the number of duplicate users: SELECT objectguid, COUNT(*) TotalCount FROM aduser GROUP BY objectguid HAVING COUNT(*) > 1; SELECT userid, samaccname, objectguid, COUNT(*) TotalCount FROM aduser GROUP BY userid, ...