Univention Bugzilla – Bug 53194
Setting the ucsschoolAdministrator should automatically adjust the school_admin role
Last modified: 2022-06-08 13:55:03 CEST
Since the consistency check in the diagnostic module shows the missing role e.g. for ucsschool administrators, we should make sure the role is set properly, when setting the ucsschoolAdministrator flag. At the moment the role is not set automatically, and can only be set via udm, not via UMC, because the extended attribute ucsschoolRoleUsers is invisible by default.
From my point of view all the marks (Admin, teacher, student, staff) in UMC should also trigger also the attachment of the role. This is what every customer expects by setting the mark.
(In reply to Dirk Schnick from comment #1) > From my point of view all the marks (Admin, teacher, student, staff) in UMC > should also trigger also the attachment of the role. This is what every > customer expects by setting the mark. When the UCS@school UMC modules are used, that happens. When non-UCS@school UMC modules are used it doesn't. Other things are then also not set correctly. That's why school customers should only use the UCS@school UMC modules. Also: changing the role of a user is *not* supported. With one exception: making a staff/teacher an admin.
(In reply to Daniel Tröder from comment #2) > (In reply to Dirk Schnick from comment #1) > > From my point of view all the marks (Admin, teacher, student, staff) in UMC > > should also trigger also the attachment of the role. This is what every > > customer expects by setting the mark. > > When the UCS@school UMC modules are used, that happens. > When non-UCS@school UMC modules are used it doesn't. Other things are then > also not set correctly. That's why school customers should only use the > UCS@school UMC modules. > > Also: changing the role of a user is *not* supported. With one exception: > making a staff/teacher an admin. I am confused. Using the UCS@school UMC modules means getting redirected to the ldap-directory-module, using the advanced settings button and changing the user there. this is afaik the same module like the "normal" user module. So it is not possible to work? Adding a teacher via UCS@school UMC modules it is not possible to set a role a role at all, the field is not editable. Or am I on the complete wrong way?
The endusers will use the non school users module. They did it and they will do. As far as it is useable and as far as there is any @school attribute to configure, the will not get the problem. Also Christinas statement applies to me.
What I am saying is that using a non-school-UMC module to change a school-attribute is not supported unless it is to make a user an administrator. That customers do unsupported things does not change the fact, that it is not supported.
BTW: we will address this particular issue: creation of school admins with correct role attribute. Because customers should not have to use a non-school-UMC module to change a school-attribute.
I think our product should be robust and we should prevent such missunderstandings. F.e. Removing all school settings from the normal users module and give the possibility to set everything in a school users module. Also possible in my mind is a banner that this module is not for creating/modifying school users in the normal users module. Our customers are not aware about the "do not use the users module in school environment" and I can understand them, as there is a users module, so I can use it to do create or modify users. The best way from my point of view would be to upgrade the users module to use it; also in a school environment. The marks in the users module (Apps -> UCS@school Administrator, UCS@school Examuser, UCS@school Staff, UCS@school Student, UCS@school Teacher) are missleading; what are they doing at all? There is a consistency check a student can not be an Admin, but if I set a mark I see no change in the user config. Customers are expecting to set the role of the user there. If they are useless, hide them. We can point to the documentation, but don't we want a self speaking product without such missunderstandings? Also pointing to the docs will not help us in the support team ;-)
(In reply to Dirk Schnick from comment #7) > I think our product should be robust and we should prevent such > missunderstandings. > > F.e. Removing all school settings from the normal users module and give the > possibility to set everything in a school users module. > > Also possible in my mind is a banner that this module is not for > creating/modifying school users in the normal users module. I also think that would be good, but it has been discussed before and was rejected. (I think for technical reasons.) Maybe we can reopen the discussion by collecting all requirements for a compete school admin UI.
(In reply to Daniel Tröder from comment #8) > I also think that would be good, but it has been discussed before and was > rejected. (I think for technical reasons.) > Maybe we can reopen the discussion by collecting all requirements for a > compete school admin UI. I think we reopened the discussion already. ;) Waiting for PO's statement. I have written what is happening and what will happen if we do not change anything here. I'm sure there will be some technical Challenges, but a change in any way seems to be necessary.
This still occurs in UCS 5.0-1. A customer opened a support ticket for that issue