2018-01-08 14:11 GMT+01:00 Thorn, Colin <[email protected]>: > Dear Clément, > > so LSC does not provide the possibility to decode base64 before writing it > into the destination LDAP?
The base64 value is just in the LDIF output. LSC reads value directly in LDAP where there is no base64 encoding, so LSC does not need to decode value. > Regarding the Error: > > I checked the schema for the four objectclasses (inetOrgPerson, > organizationalPerson, person, top) I am using and found all using the > following command: > ldapsearch -H ldap://ldap.mydomain.com -x -s base -b "cn=subschema" > objectclasses > > objectClasses: ( 2.5.6.0 NAME 'top' DESC 'top of the superclass chain' > ABSTRACT MUST objectClass ) > objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' DESC > 'RFC2798:..... > objectClasses: ( 2.5.6.6 NAME 'person' DESC 'RFC2256....... > objectClasses: ( 2.5.6.7 NAME 'organizationalPerson' DESC > 'RFC2256:.................. > Ok, but check the objectClass values from your source object. One of them may not be a standard object class. Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
