Hi,
I have set up the LDAP data collector.
I can collect the data from an AD server and sync it with itop.
But when an account disappears from the AD it cannot be deleted when synch process is running.
I get this error msg:
Unable to delete the destination object: The field Person is not writable because it is mastered by the data synchronization. Value not set.
When the synch process is running again later, this Person is deleted without error.
So it always needs 2 runs to delete a Person in iTop.
Compared to the user entry belonging to this Person in iTop, this is deleted without error in the first run after disappearing.
What could this be?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is indeed a 'normal behaviour' :) To be able to link a new user to a new person, the person has to be created first. So the LDAP Sync first do the 'Person' sync', then the 'User' Sync. This is the good way to do that wxork.
But, in case of a suuppression, it would be better to first suppress the user, then the Person. Unfortunatelly it doesn't work this way.
Workaround for those noisy messages : instead of suppressing the Person, just obsolete it, and saying plan the effective suppression 2 days later (if your sync runs every day),
It's fairly easy to do with a manually builded sync, it's allitle more tricky with sync that are auto generated, but after some wild guess, you should be able to manage the two or three changes to do in the {something like Person}.json file.
Sorry to be unprecise but we don't use the LDAP sync anymore, I don't have more precise informations.
Pascal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have set up the LDAP data collector.
I can collect the data from an AD server and sync it with itop.
But when an account disappears from the AD it cannot be deleted when synch process is running.
I get this error msg:
When the synch process is running again later, this Person is deleted without error.
So it always needs 2 runs to delete a Person in iTop.
Compared to the user entry belonging to this Person in iTop, this is deleted without error in the first run after disappearing.
What could this be?
Hi Nico,
This is indeed a 'normal behaviour' :) To be able to link a new user to a new person, the person has to be created first. So the LDAP Sync first do the 'Person' sync', then the 'User' Sync. This is the good way to do that wxork.
But, in case of a suuppression, it would be better to first suppress the user, then the Person. Unfortunatelly it doesn't work this way.
Workaround for those noisy messages : instead of suppressing the Person, just obsolete it, and saying plan the effective suppression 2 days later (if your sync runs every day),
It's fairly easy to do with a manually builded sync, it's allitle more tricky with sync that are auto generated, but after some wild guess, you should be able to manage the two or three changes to do in the {something like Person}.json file.
Sorry to be unprecise but we don't use the LDAP sync anymore, I don't have more precise informations.
Pascal
Hi Pascal,
thanks for your detailed explanation. I will test what you propose.
Cheers,
Nico