We should first fix this in 5.2-3 and then backport to 5.0-10 via Bug #58737. +++ This bug was initially created as a clone of Bug #58737 +++ A sAMAccountName change doesn't update `DN Mapped CON` cache and then a subsequent change of CN (leading to a modrdn DN change in AD) causes a traceback in the connector-ad.log, because the connector doesn't find the cached `olddn` (AD-DN mapped to UCS-DN) because it doesn't match reality any more. But even during the first step there's already a traceback, because the `post_ucs_modify_functions` can't find the object any longer using `ucs_object['dn']`: [...]
f6364263fb4 | feat(ad-connector): update object['dn'] in modify_in_ucs a23812a0cf7 | test(adconnector): AD-Connector cache 'DN Mapping CON' update on uid change Package: univention-ad-connector Version: 16.4.4 Release: 5.2-0 Scope: errata5.2-3 Package: ucs-test Version: 12.3.24 Release: 5.2-0 Scope: errata5.2-3
Looks good to me Jenkins: OK Manual test: OK yaml: OK
<https://errata.software-univention.de/#/?erratum=5.2x276>