Univention Bugzilla – Bug 34205
S4 connector overwrites changes by import hooks
Last modified: 2014-03-07 15:10:31 CET
In a single master scenario, I created a number of import hooks that subsequently modify an imported user. The third hook sets the attribute mailPrimaryAddress. All the hooks run properly and don't throw any errors but the resulting object doesn't have the attribute mailPrimaryAddress set. I experimented with a sleep call in the import hook and it work. Talking to our S4 connector experts I discovered that the connector is actually responsible for this behavior. As a workaround for the single master scenario the S4 connector has to be stopped before import and started after it finished. For the master slave scenario this is much more difficult, because on every DC Slave a S4 connector is running.
(In reply to Jan Christoph Ebersbach from comment #0) > Talking to our S4 connector experts I discovered that the connector is > actually responsible for this behavior. As a workaround for the single > master scenario the S4 connector has to be stopped before import and started > after it finished. For the master slave scenario this is much more > difficult, because on every DC Slave a S4 connector is running. In a master slave szenario the master's notifier may be stopped prior to the changes. If all changes are done and the notifier is started again, the ldap objects fetched by the school slaves do not change between the replication steps. If I'm not wrong, this should also bypass the S4 connector problems.
I think it is a duplicate of Bug #33621. *** This bug has been marked as a duplicate of bug 33621 ***