Univention Bugzilla – Bug 46757
AD-Connector rejects to sync object to_ucs probably due to adopted AD schema
Last modified: 2020-07-03 20:52:48 CEST
+++ This bug was initially created as a clone of Bug #46751 +++ When syncing a MS/AD to a UCS/LDAP some objects are rejected with the following TraceBack: ---------------------------------------- 26.03.2018 06:25:14,6 LDAP (ERROR ): Unknown Exception during sync_to_ucs 26.03.2018 06:25:14,10 LDAP (ERROR ): Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/univention/connector/__init__.py", line 1367, in sync_to_ucs f(self, property_type, object) File "/usr/lib/pymodules/python2.7/univention/connector/ad/password.py", line 311, in password_sync_kinit object = connector._object_mapping(key, ucs_object, 'ucs') File "/usr/lib/pymodules/python2.7/univention/connector/__init__.py", line 1691, in _object_mapping object_out['attributes'][self.property[key].post_attributes[attr_key].con_attribute] = self.property[key].post_attributes[attr_key].mapping[0](self, key, object) File "/usr/lib/pymodules/python2.7/univention/connector/ad/proxyAddresses.py", line 70, in to_proxyAddresses mailPrimaryAddress = object['attributes'].get('mailPrimaryAddress', [None])[0] IndexError: list index out of range ---------------------------------------- As far as I understood the scenario, there is Kerio Mail installed on the MS/AD system and should be migrated to a UCS/Kopano - which obviously seems to be already setup. There is also the MS/AD object at hand.
Probably the Patch from Bug# 46751 could also applied here.
We will fix it through Bug #46751 for UCS 4.3- Is a backport to UCS 4.2 still needed?
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.