Univention Bugzilla – Bug 51283
unstable UMC App-tab leads to lost LDAP data
Last modified: 2021-08-31 08:14:41 CEST
The handling of the virtual UDM option introduced in UCS 4.4-0 is not stable in UMC. Sometimes changing a users password leads to the deletion of all extended attributes of an app from the usesr LDAP object! UDM then logs: "__setitem__: Ignoring property <ext.attr>" This happens for all apps in UCS. But it only becomes visible for those that use more than one ext. attribute. Sometimes a UDM hook will prevent the user from being saved, because the deleted attribute must not be empty, but the administrator cannot work around that, because in the UMC the property seems to be set. The result can be especially problematic, when the deleted attribute leads to errors in connected software like listener modules. For example in the OX app tracebacks happen in the listener module. The error does not happen when changing properties through with the UDM command line utility or through Python.
*** Bug 50469 has been marked as a duplicate of this bug. ***
We had tests and discussions around fixing this issue. As of now all attempts to fix the race condition either were not successfull or changed the API for ISVs and/or UDM REST API. At the point in time where we decided to fix the OX integration by moving attributes from the App Tab to "normal" extended attributes we were unaware that the problem exists also for other Apps.
(In reply to Ingo Steuwer from comment #5) > We had tests and discussions around fixing this issue. As of now all > attempts to fix the race condition either were not successfull or changed > the API for ISVs and/or UDM REST API. The UDM REST API is not affected by fixing this correctly (aka. using real extended options) because the UDM REST API already exposes the fake extended options. > At the point in time where we decided to fix the OX integration by moving > attributes from the App Tab to "normal" extended attributes we were unaware > that the problem exists also for other Apps. The openproject problem was already known at this point and we mentioned it when discussing how to fix the OX problem.