Univention Bugzilla – Bug 46972
S4-connector removes extended attribute that were added after the last connector restart
Last modified: 2018-06-06 16:16:29 CEST
Created attachment 9522 [details]
connector log with debug level 4
Reproducer: UCS 4.3 with samba4
Install owncloud. A new extended Attribute is added during installation. All existing users should now be activated for ownCloud with the LDAP attribute ownCloudEnabled=1. The extAttr default is 1, so all new users should be enabled as well.
Result: Users are created with ownCloudEnabled=1. After some connector cycles, the LDAP attribute disappears.
See debuglevel 4 logfile, existing user=Administrator, new user=univention.
At timestamp 07.05.2018 16:15:46,249 the user univention seems to be modified and the ownCloudEnabled attribute is removed.
This also happens when joining a UCS into an AD domain during system setup! Users synced from AD are not activated for the app.
Restarting the connector solves the issue.
When no samba4 is installed, the issue does not occur.
* restart connector if previous object was extended attribute
* restart connector in postrun if extended attribute has been modified
(and connector not yet restarted)
seem to be enough for owncloud
created bugs for ad connector (Bug #47049) and for 4.2-4 (Bug #47050, Bug #47048)
Ok, looks good, advisory too.