Univention Bugzilla – Bug 32962
Two way sync of binary objects
Last modified: 2019-03-25 20:57:17 CET
Currently, when syncing binary objects currently only works oneway by adding into the mapping entries like 'userCert':univention.s4connector.attribute ( ucs_attribute='userCertificate', ldap_attribute='userCertificate;binary', con_attribute='userCertificate' ), This however prevents a two way sync as the attribute doesn't have the binary in the end. Therefore it would be good, if the connector would be extended to allow the sync of binary objects.
"one way": which way? Logs?
It only syncronizes from UCS to S4 on the way back the following error occures 22.10.2013 14:50:45,870 LDAP (PROCESS): sync to ucs: Resync rejected dn: CN=Win7-02,CN=Computers,<Base> 22.10.2013 14:50:45,879 LDAP (PROCESS): sync to ucs: [windowscomputer] [ modify] cn=win7-02,cn=computers,<Base> 22.10.2013 14:50:46,10 LDAP (ERROR ): Unknown Exception during sync_to_ucs 22.10.2013 14:50:46,11 LDAP (ERROR ): Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1311, in sync_to_ucs result = self.modify_in_ucs(property_type, object, module, position) File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1178, in modify_in_ucs return ucs_object.modify() and self.__modify_custom_attributes(property_type, object, ucs_object, module, position) File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 344, in modify return self._modify(modify_childs,ignore_license=ignore_license) File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 868, in _modify self.lo.modify(self.dn, ml, ignore_license=ignore_license) File "/usr/lib/pymodules/python2.6/univention/admin/uldap.py", line 412, in modify raise univention.admin.uexceptions.ldapError, _err2str(msg) ldapError: Invalid syntax: userCertificate;binary: value #0 invalid per syntax
You can simple overwrite the mapping functions in mapping.py. Alternative you can add post-functions.
This issue has been filed against UCS 3.1. UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please reopen.