Univention Bugzilla – Bug 56152
Import naming scheme can lead into not working usernames (in Windows machines) f.e. con.*
Last modified: 2023-08-03 16:03:40 CEST
+++ This bug was initially created as a clone of Bug #53519 +++ In Windows, there are some names that are reserved for special use (https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file). With our freely definable scheme in our import, we allow user names that can lead to such names. If this happens, no check takes place and diffuse errors occur under Windows. Most reserved names should be rare to non-existent, with con.* I can think of several names that can lead to such user names; as in the attached ticket. --> Ticket: https://otrs.knut.univention.de/otrs/index.pl?Action=AgentTicketZoom;TicketID=1117746# Breaking Change for existing Users in the school database / no import is possible
Fixed with commit ff81544faefbff79e514e928d72fe6cf6b1a20f5 as of 20.07.2023: Package: ucs-school-umc-diagnostic Version: 2.0.14 Package: ucs-school-lib Version: 13.0.38 Changes which were introduced: - A UCR variable ("ucsschool/validation/username/windows-check") with which administrators can manually enable or disable the new validation - A check in the joinscript which automatically enables the this UCR variable if all present usernames are compliant and the variable is not already set - A script which is used in the joinscript which can be manually used by Administrators to list all non-compliant usernames
Versions are Package: ucs-school-umc-diagnostic Version: 2.0.15 Package: ucs-school-lib Version: 13.0.39
UCS@school 5.0 v4 has been released. https://docs.software-univention.de/ucsschool-changelog/5.0v4/de/changelog.html https://docs.software-univention.de/ucsschool-changelog/5.0v4/en/changelog.html If this error occurs again, please clone this bug.