Univention Bugzilla – Bug 31804
Generic activation
Last modified: 2017-03-22 09:19:17 CET
We should think about a way to get a generic activation for app vendors (ISV). For example, the ISV can define in the ini file whether computers or users should be activated for the app. We add a new multi value attribute to univentionObject, for example univentionActivatedApp. Via UDM CLI or UMC the AppID can be written to the attribute. The activation should be on one tab in UMC. Some apps will still have its own schema extensions. I think that will be OK.
Which apps should be listed in that Widget? Only the installed? What happens to that attribute if the application is uninstalled?
Not with UCS 3.2.
I think this is not needed anymore? The Core-Edition and the license-activation achieved this, if I understand correctly.
No, this is a generic activation for Apps, not UCS. A user object should get a checkbox "Activated for ownCloud".
Fixed in univention-appcenter 5.0.23-37.264.201701201311 GenericUserActivation=True adds a schema file defining ${app}Activated as attribute and ${app}User as objectClass. If a schema file is shipped along with the App, this file is used instead. The schema file is then registered and an Extended Attribute is added on the "Apps" tab of UDM. The Extended Attribute is a CheckBox and reads "Activate user for %s".
* Fail - extended attribute is removed during App deinstallation even if the App is installed on another machine in the domain * OK - App installation with GenericUserActivation=True on member server/master server * OK - second App with GenericUserActivation=True * OK - normal App installation * OK - deinstallation of GenericUserActivation=True App
Fixed in univention-appcenter 5.0.23-40.267.201701231816
OK - test OK - YAML OK - univention-appcenter
<http://errata.software-univention.de/ucs/4.1/389.html>