2014-10-24 17:05 GMT+02:00 Dinesh Babu <[email protected]>: > I have more info on this now. Scenario is as follows > > > > Initial state: > > Source ldap has two users > destination has no users > > user1 > > user2 > > > > I do a sync and the destination has two users( user1,user2 ). > > > > Source ldap has two users > destination has two users > > user1 > user1 > > user2 > user2 > > > > Now I add two new users ( newuser1, newuser2 ) to source ldap > > > > Source ldap has two users > destination has two users > > user1 > user1 > > user2 > user2 > > newuser1 > > newuser2 > > > > Now I change the filter so that only user names starting with new* is > included in the sync and run the sync. > > > > Source ldap has two users > destination has two users > > user1 > user1 > > user2 > user2 > > newuser1 > newuser1 > > newuser2 > newuser2 > > > > I was expecting user1 and user2 to get deleted based on my new filter ( > and this is my requirement ). I debugged LSC code and found that the only > check during clean up made is whether the entry exists in the source or not > and there is no check for filter. > > >
Hi, note that LSC separate the sync phase and the clean phase. You need to call the clean method. This method use the destination getAllFilter to get desintation entries with pivot, and use source cleanFilter to see if a corresponding entry match. If not, the destination entry is deleted. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
