Univention Bugzilla – Bug 51727
Show value as read-only in UMC while still editable with UDM CLI
Last modified: 2023-05-05 11:45:16 CEST
A feature request desired from multiple customers. Extended Attributes should have an option to make it non-changable, read-only through UMC, but still with the UDM CLI and its python modules library. The mayChange Option disables the change function for both, UMC and UDM CLI.
Do you have an example usecase?
(In reply to Ingo Steuwer from comment #1) > Do you have an example usecase? We have a customer that uses a custom import script (CSV) to import Users with extended attribute data. One of these extended attributes shall be visible inside the Users UMC module, but not editable. This script uses the python Univention module 'users/user' to create / update these Users based on the CSV data. The mentioned mayChange Option to set this extended attribute to read-only inside UMC unfortunately also sets it to read-only for the mentioned python module. --- A second customer has multiple values like a maximum mailbox usage quota for Users, that are handled by external services (dovecot) and shouldn't be writeable inside UMC. This customer needs to use two attributes per value to achieve this feature. The first attribute actually contains the data changable and is used to manage it (mayChange=1). The second one only exists to display the value inside the UMC module read-only (mayChange=0). An UDM handler needs to use LDAP to transfer the data to this attribute only for its UMC module display. It would be great to have these attributes managable through the UDM python library and all its features, while still displayable inside the UMC module as read-only.