• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 1574 views
  • Users 0 members are here
Options
Related

How to effectively filter the import of data using LDAP Connector

leonilson lopes1
over 4 years ago

Hello Comunity,

I'm performing some tests in a LDAP connector.

In order to make it quickly, I included a filter in the "scope" option to retrive only 2 objects, the aim of my testing.

It works fine for reporting, which is generated instantly. However, when I run it for real, it seems 1IM will read everything to apply the filter later, making it to take a long time to finish the process.

Is it possible to really filter the importing so that 1IM only retrieves what specified in the filter?

Best Regards.

  • 0 over 4 years ago

    Hi,

    Two types of filter are supported; System filter and Object filter

    The System filter is applied to the request for the data from the target. So here you should specify the LDAP filter for the objects you want to retrieve.

    The Object filter is applied to the data after it has been retrieved from the target.

    It sounds like you need a System filter.

    HTH, Barry.

  • 0 over 4 years ago in reply to Barry Jackson

    Hello Barry,

    Thank you for your answer.

    Actually, I had followed this description I did exactly this, a "System Filter", but I got the behavior I described. Clearly the connector is reading all the base and applying the filter later.

    However, there is another warning "This filter only works when loading existing system objects", which make me think that I need to go through a full sync first and then the filter will work. But, in my case, I'm connecting to this LDAP only to grab some auxiliar information, which means that it never creates an object... So I think that is the reason it never works for me. 

    If anyone can confirm if this interpretation is correct and if there is a way to speed this up, I would appreciate!