Univention Bugzilla – Bug 50496
Hide the default Computer, User and Groups in ucs@school environments
Last modified: 2023-06-12 14:02:46 CEST
Very often we have issues with LDAP objects (users, groups or computers) which have not been generated with the schoollib (UMC: Computers(School) or Importer). Instead they have been added through the "usual" UCS-Ways outside of ucs@school. VERY frequently we have severe issues with these objects. They are lacking the correct attributes or are lcated at the wrong place and cause crashes. Can we hide the "default" modules or change them so the users will create proper ucs@school objects?
I don't think it's advisable to hide administration tools from privileged users. They do require them anyway, to edit any attribute that is not available in the school-umc-wizards. We could instead show a warning when they want to create such objects through the non-school-modules. Additionally we should write system diagnose tests, that help find and fix problematic objects. The first one may already be on its way for Bug #50349.
An idea: We could add a message/popup in the normal users/users UMC module which will be shown in case UCS@school is active and informs the user that pupils/teachers should not be created with this module.
I like that idea. Maybe in UCS a hook could be searched in the "add-user" UMC call and in UCS@school we'll install the hook implementation. The hook mechanism should allow for multiple implementations to be called one after the other until all complete or one raises an exception.
I don't know if it's done with a warning. It's all about the use case "ADD". If UCS@school is installed, would it be possible to display a "ADD SCHOOL USER" button to the left of the normal "ADD" button? The "ADD SCHOOL USER" button would then open the @school "User (Schools)" wizard.