Univention Bugzilla – Bug 46529
UMC does not recognize autofilled values for UDM objects, does not save changes
Last modified: 2018-05-25 14:38:58 CEST
See also bug #41053.
When opening an UDM object and some required values were not set at the object, the values were set to their default values, and a popup informed the user about it. When save was clicked, the change were applied.
Testcase: ucs4.2-3e311; Install kopano, open Administrator user. On the kopano tab the role Kopano user is shown. But an ldapsearch and udm user list show that the attribute is undefined.
The UMC udm/get query returns the default value for the attribute: kopano-role
: "user", which is wrong. No change is detected, and one cannot save the object that way. To enable the user, one has to configure a different role, save, reopen, set user role, save.
I would expect that upon opening the user object a popup informs the user that no attribute was defined and the default value was set. When clicking change, the modification should be applied.
patch at: jkeiser/46529_umc_does_not_recognize_default_values
The get() method for an UDM object now returns the properties for which a default value was set. The UDM Detailpage uses that information to show the popup again, which informed the user about values that had default values set.
The users/user object has two properties with default values that do not get saved directly.
'unlock' is just a trigger and has no mapping to ldap.
'homeSharePath' which is used for automountInformation is only saved when 'homeShare' is a also set.
At least for 'unlock' the popup would appear every time to inform the user that the default value for 'unlock' has been set.
A flag to prevent the popup for specific properties has been added.
I did not find another objecttype where a property has a default value but no ldap mapping (which would lead to the same problem has 'unlock' for users/user)
Created attachment 9509 [details]
0f77c31 Bug #46529: Notify about set default values in UMC
7b28e0c Bug #46529: Restore 4.2-3 behaviour for setting automount objectclass
152f362 Bug #46529: Debian changelog
8a6ab15 Bug #46529: YAML entry
df22826 Bug #46529: Merge branch 'jkeiser/46529_umc_does_not_recognize_default_values' into 4.3-0
61d8d39 Bug #46529: YAML update version
7b28e0c Bug #46529: Restore 4.2-3 behaviour for setting automount objectclass:
after homeSharePath (with the default value of <username>) was no longer ignored when saving i got this error message when trying to save: "Das LDAP-Objekt konnte nicht gespeichert werden: LDAP-Fehler No such attribute: modify/delete: objectClass: no such value"
This was due to the 'automount' objectclass missing. In 4.2-3 it was added when 'homeShare' or 'homeSharePath' was modified. I fixed what i believe was a typo.
32d5659 Bug #46529: make shouldPreventPopupForEmptyPropWithDefault call safe
65de35a Bug #46529: Debian changelog
8a38ee2 Bug #46529: YAML update version
Tests: OK: I was able to reproduce the original report. It has been fixed with the latest est errata packages.
Package "univention-management-console-module-udm.yaml" is WIP with incomplete YAML.
arequate@omar:~/git/ucs/doc/errata/staging$ less univention-management-console-module-udm.yaml
This update addresses the following issue(s):
* Properties that have been set to default values are no
longer ignored when saving from the UDM detail page.
I've added the missing src: value
608752ac9f | Fix inclomplete advisory