Le 23/07/2015 10:46, Thomas Peter a écrit :
Hi Clément,
On 2015-07-21 17:04, Clément OUDOT wrote:
you must escape the DN, see
http://lsc-project.org/wiki/documentation/latest/upgrade#dn_escaping
m( thnx! fixed. :)
I also not that the objectClass attribute is not present. You must
create it else the entry will be rejected.
But I don't see why the objectClass attribute is not created.
I thought I could hardcode it to "inetOrgPerson" via
<dataset>
<name>objectClass</name>
<policy>FORCE</policy>
<forceValues>
<string>"organizationalUnit"</string>
<string>"top"</string>
</forceValues>
<delimiter>,</delimiter>
<name>objectClass</name>
<policy>FORCE</policy>
<defaultValues></defaultValues>
<forceValues></forceValues>
<createValues>
<string>"inetOrgPerson"</string>
</createValues>
<delimiter>,</delimiter>
</dataset>
Declare objectClass in <fetchedAttributes> in your destination service,
and configure the dataset like this:
<dataset>
<name>objectClass</name>
<policy>KEEP</policy>
<createValues>
<string>"inetOrgPerson"</string>
<string>"organizationalPerson"</string>
<string>"person"</string>
<string>"top"</string>
</createValues>
</dataset>
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
87, rue de Turbigo - 75003 PARIS
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
