At the example of Bug 50033 we found out, that it's hard to add properties to UDM in an errata update, because a customer could have defined an extended attibute that conflicts with the UDM property. I see three cases, I'll explain at the example of an property "initials", which should be mapped to the LDAP-attribute "initials": Case 1) Extended Attribute does exactly the same, mapping the LDAP attribute "initials" to the UDM property of the same name Case 2) Extended Attribute maps the LDAP-Attribute "initials" to the UDM property with a different name (e.g. "myInitials") Case 3) Extended Attribute maps the UDM property "initials" to an LDAP attribute with a different name (e.g. "univentionFreeAttribute7") My impression is that it should be technically possible to handle this in a better way that doesn't result in undefined behaviour that causes trouble e.g. for The S4-Connector.
Created attachment 10168 [details] Some starting point
This issue has been filed against UCS 4.4. UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.