Do we need Scheduled LDAP user import when listener is on?

[_zg_r T_rker]

In LDAP Server when tou start listener, listener checks for the Updates in the Active Directory. When listener sense an Update or new record in AD it updates the user record. My qusetion: Do we need an extra scheduled LDAP import when listener is on? What is the purpose of scheduled user import?

Best Regards,

í–zgür

[kevinray]

Yes. You need to schedule a Scheduled Load to run the query as often as you wish. We have this run every 2 hours in our environment. This is the actual job that goes and, query's and pulls the data back into an import set.

The listener is making sure your connection to the LDAP server is good

[Goran WitchDoc · Accepted solution]

The listener is sitting there watching in real time.. when change is happening, the listener will pick it up and update ServiceNow. So in the best of worlds, you shouldn't need a scheduled job as well.. Me.. I like have a backup plan. So I would recommend to have a scheduled job as well, to make sure the listener didn't miss anything. How often... well at least of peak hours and perhaps once a week. Depending on things like size, relevance from business etc.

//Göran

[Vladi1]

We had LDAP integration at my previous work. Listener was active non stop and we had daily LDAP import little bit after midnight.