LDAP Server with three OU definitions retrieving same data on all

Jonas Lundsholm
Mega Contributor

‎11-05-2018 03:22 AM

I've got an LDAP server configured which I'm able to browse and load records from.

The LDAP server has three different OU Definitions, with three different RDN's. All of them use "sAMAccountName" as Query field and they are pointing to the sys_user table.

find_real_file.png

If I navigate to the OU Definitions and select "Browse" from the Related links I'm able to view the matching data from each OU. But if I go to the related Data Source and select "Load All Records" I get the same result using all three data sources.

How come I am able to view the correct data when browsing the different OU definitions, but when actually loading records to an import table all three data sources (that are using those OU definitions) load the exact same records?

find_real_file.png

Any help is much appreciated.

Preview file
18 KB
Preview file
19 KB
0 Helpfuls
  • 2,213 Views
12 REPLIES 12

Michael Fry1
Kilo Patron
In response to Jonas Lundsholm

‎11-06-2018 05:12 AM

In your screen post - Starting dir - can you use that for your RDN? Again your filter will limit your results so there isn't a reason to have a OU per country. Just get to the point where one query will see all records regardless of OU.

Jonas Lundsholm
Mega Contributor
In response to Michael Fry1

‎11-06-2018 05:35 AM

You are correct, I can get all the users without needing three separate OU definitions, if I start the query from higher up in the structure and use a filter.

However it is not desired to import all user objects from AD, only the specific User OUs located under certain countries.

And since you are able to configure multiple OU definitions per Server, I think it is supposed to work with configuring three definitions to look in three separate OUs.

0 Helpfuls

Jonas Lundsholm
Mega Contributor
In response to Jonas Lundsholm

‎11-06-2018 01:31 AM

So far the only workaround I've found for this is to remove all OU definitions except one. I use that OU definition as the LDAP Target for all Data sources. In between importing data from each Data source I have to go and edit the RDN in the OU definition and set it to the correct OU.

I'm hoping this is a bug in the current release and patch, and that it will be fixed in the future.
The instance I'm working with is running Kingston patch 7.

The issue is preventing scheduled imports because the OU definition has to be manually updated for each Data source.

0 Helpfuls