Le 25/05/2016 13:23, Gustavo Castelo a écrit :
Hi,
I'm using asyncLdapService with AD, which is working well for modified
fields but doesn't receive delete notifications. I can see in
wireshark that nothing comes through from AD when an object is
deleted, so I'm wondering if it's a problem in AD or the way the
listener is registered?
Using LSC 2.1.
This is my configuration:
<asyncLdapSourceService>
...
<baseDn>CN=Users,dc=windows,dc=acrossgadget,dc=com</baseDn>
..
<pivotAttributes>
<string>mail</string>
</pivotAttributes>
<fetchedAttributes>
<string>mail</string>
<string>memberOf</string>
<string>userAccountControl</string>
</fetchedAttributes>
<getAllFilter><![CDATA[ (objectClass=*) ]]></getAllFilter>
...
<synchronizingAllWhenStarting>false</synchronizingAllWhenStarting>
<serverType>ActiveDirectory</serverType>
</asyncLdapSourceService>
Thank you
Hi,
delete is not managed by the async phase (-a), you need to run the clean
phase (-c) to delete entries. It means that deletions will not be pushed
directly to your destination, you need to run the clean phase as a cron job.
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
87, rue de Turbigo - 75003 PARIS
Blog: http://sflx.ca/coudot
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
