Univention Bugzilla – Bug 43060
UMC reverts objects silently
Last modified: 2020-06-22 12:50:33 CEST
If one open a object in UMC, makes some modifications (e.g. the groups of a user) and saves the object AND in the background these attributes were changed, too (e.g. because some UCS@school exam users were added to a school-class) all these modifications get lost. HTTP defines conditional requests to prevent such errors: We could set E-Tag or Last-Modified in the request udm/get. We could set If-None-Match or If-Unmodified-Since in the request udm/put. If these don't match we can respond with HTTP Error 412 - Precondition failed. Every LDAP object has an attribute "modifyTimestamp" which can be used for the last-modified time. We can also generate an hash of the object as an Entity-Tag.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.