Hey,
This is due to how the UMC and the Kopano attributes work. If the underlying LDAP attribute (in this case: kopano-role) is unset, the drop-down box will have its default value selected. The default value is “Kopano user”.
Now one would think that this change in value (from unset to “Kopano user”) should be saved when you hit the “save” button, but until recently there was a bug in the UMC regarding default values for attributes. This bug has been fixed in UCS 4.3 errata 88 and 89.
What happens when you do the “change, save, change back, save again” dance is:
- Initially the LDAP attribute is unset, the drop-down box shows the default value instead of the current value (unset).
- You change the value to a non-default and save. With this you circumvent the aforementioned UMC bug. The UMC recognizes a change in attribute value and sets the
kopano-roleattribute to “none”. - You change the value from “none” to “Kopano user”. As the LDAP attribute is set, the UMC bug is again not triggered. The UMC recognizes the change from “none” to “Kopano user” upon saving and sets the LDAP attribute accordingly.
The same issue was a topic in this thread, too (in German). There are some more details there.
Kind regards,
mosu