During the QA of univention/dev/ucs#2912 is has been noticed that the exam mode is not using UDM for creating the exam users but copies and adds them via direct LDAP. This breaks the new univentionObjectIdentifier feature that will be activated and enforced with UCS 5.2-2. The exam-master module simply copies the univentionObjectIdentifier of the school user to the new exam user which violates the uniqueness of univentionObjectIdentifier. It has been decided together with the UCS team, that 1) exam-master is adapted to deal with the new attribute correctly (create a new value for the object instead of copying it). 2) the improved exam-master code will be released as UCS@school 5.2v3. 3) UCS 5.2-2 will refuse to install if an unaltered UCS@school version is installed (UCS@school 5.2v1 or 5.2v2). 4) UCS@school 5.2v1 and UCS@school 5.2v2 will get a preinst script, that refuses the installation of those versions on UCS 5.2-2. This bug is dealing with item 2)
Just for completeness (even if it's not part of this bug): Item 4) has been dropped. There are technical difficulties that prevent the described solution.
A fix has been implemented in ucs-school-umc-exam 12.0.5 ucs-test script has been adapted to check if the univentionObjectIdentifier of the exam user is different from the one of the originating user Manual tests: After an exam in DEMOSCHOOL in DEMOCLASS has been started: root@master:~# univention-ldapsearch -LLL uid=* univentionObjectIdentifier [...] dn: uid=demo_student,cn=schueler,cn=users,ou=DEMOSCHOOL,dc=ucs,dc=test dn: uid=max.muster,cn=schueler,cn=users,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: b1920bcf-39a6-4db3-b6c5-5324b2cf8471 dn: uid=berta.beispiel,cn=schueler,cn=users,ou=DEMOSCHOOL,dc=ucs,dc=test dn: uid=victor.vorlage,cn=schueler,cn=users,ou=DEMOSCHOOL,dc=ucs,dc=test dn: uid=erika.example,cn=schueler,cn=users,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: 94749961-8ce4-462e-8351-0bb4eb497148 dn: uid=exam-demo_student,cn=examusers,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: 800f91ec-617f-4e4e-a535-a89c017272a5 dn: uid=exam-max.muster,cn=examusers,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: ca5a7a85-27f4-48da-b4c4-59fc2151d2d4 dn: uid=exam-berta.beispiel,cn=examusers,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: 66a388d5-bd6b-453c-abab-6739d7449b92 dn: uid=exam-victor.vorlage,cn=examusers,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: bd1a40bb-63d8-4a40-8963-84258912d532 dn: uid=exam-erika.example,cn=examusers,ou=DEMOSCHOOL,dc=ucs,dc=test univentionObjectIdentifier: a690d0ce-0708-41e1-9c5c-d31f09567914 Every exam user has a new UUID4 as univentionObjectIdentifier no matter if the originating user had a univentionObjectIdentifier value set. → FIXED
Tested with a teacher on multiserver 5.2-1 and singleserver 5.2-2: univentionObjectIdentifier is set for exam users -> OK
UCS@school 5.2 v3 has been released. - https://docs.software-univention.de/ucsschool-changelog/5.2v3/en/changelog.html - https://docs.software-univention.de/ucsschool-changelog/5.2v3/de/changelog.html If this error occurs again, please clone this bug.