Hi,
another test today: I have an asyncLdapSourceService, and I want to
force the objectClass values on entry creation, but keep existing
values for existing entries.
So I have this dataset:
<dataset>
<name>objectclass</name>
<policy>KEEP</policy>
<createValues>
<string>"inetOrgPerson"</string>
<string>"organizationalPerson"</string>
<string>"person"</string>
<string>"top"</string>
</createValues>
</dataset>
When synchronizing, I have an error because the created objectClass
values are the values from the source entry. Of course, source entry
object classes are not compatible with destination object classes
(imagine OpenLDAP and AD synchronization)
I searched the reason: in async mode, the list of fetched attributes
is ignored, all source attributes are fetched, including the
objectclass attribute. And despite the dataset configuration of
objectclass, the source objectclass is used.
By replacing asyncLdapSourceService by ldapSourceService, it works. I
confirm that objectclass is present in destination fetched attributes
and not in source fetched attributes.
What do you think, should I open an issue?
Clément.
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
