Univention Bugzilla – Bug 48493
office365 user listener creates tracebacks when resyncing
Last modified: 2020-02-13 09:50:30 CET
Whenresyncing the user listener, for every user that is _not_ activated for office365 a traceback occurs: ------------------------------------------------------------------ 18.01.19 11:06:56.232 LISTENER ( PROCESS ) : o365: new and not new_enabled -> DEACTIVATE (uid=demo_student,cn=schueler,cn=users,ou=DEMOSCHOOL,dc=schulen-univention,dc=intranet) Traceback (most recent call last): File "/usr/lib/univention-directory-listener/system/office365-user.py", line 335, in handler deactivate_user(ol, dn, new, old) File "/usr/lib/univention-directory-listener/system/office365-user.py", line 262, in deactivate_user ol.deactivate_user(old) File "/usr/lib/pymodules/python2.7/univention/office365/listener.py", line 172, in deactivate_user object_id = self.find_aad_user_by_entryUUID(old["entryUUID"][0]) KeyError: 'entryUUID' 18.01.19 11:06:56.232 LISTENER ( WARN ) : handler: office365-user (failed) ------------------------------------------------------------------ The reason is, that the listener assumes it must be a modify or delete opration and expects to find the entryUUID und the "old" dictionary. In the case of a resync all operations are "new" with an empty "old".
[4.3 d5495c3] Bug #48493: fix traceback in case of resync
Verified
Closed: Released with App Version 3.0 for UCS 4.4