Univention Bugzilla – Bug 51622
Listener module for UDM extensions removes incompatible LDAP objects
Last modified: 2021-05-25 16:03:23 CEST
The listener module for UDM extensions must carefully check the attributes ucsversionstart and ucsversionend of registered LDAP objects on the Primary Directory Node/Domain Controller Master. For objects that do not fulfill the following conditions, the active flag is not set TRUE. Instead, the LDAP object is deleted from LDAP directly by the listener: - ucsversionstart > 5.0 → no check of ucsversionend - ucsversionend=4.99 → no check of ucsversionstart - ucsversionstart < 5.0 and ucsversionend != ""
This prevents the registration of incompatible UDM extensions by e.g. UCS4 apps that have not (yet) been prepared for UCS5.
The manual has to be adapted accordingly.
43a72a9d8c | Minor refactoring 897874a78c | Remove objects that don't signal Python3 support 8f593759fd | Test cases 8c587aeaa1 | Tests for Py2/3 UDM extension module handling ef6182ab1a | Changelog 5f4346aedf | fixup c1b1fb67b9 | Default --ucsversionstart 5.0-0 for univention-* packages 765268d011 | Tests And there is this commit for univention-s4-connector by Florian to make the modules survive the UCS 5.0 installation: 3ac4dcf940 | set ucsversionend Adjustment of manual after initial QA, please reopen.
1187edac61 | Revert --ucsversionstart 5.0-0 default for univention-* packages
Code and tests are looking good -> OK Changelog -> Added -> OK -> Verified
UCS 5.0 has been released: https://docs.software-univention.de/release-notes-5.0-0-en.html https://docs.software-univention.de/release-notes-5.0-0-de.html If this error occurs again, please use "Clone This Bug".