Bug #32

[ldap2ldap] Source objectClass is created in destination directory

Added by Clément Oudot over 1 year ago. Updated 10 months ago.

Status:Closed Start:16/02/2009
Priority:Normal Due date:
Assigned to:- % Done:

100%
Category:Sample
Target version:1.2.0
Problem in version:

Description

When running an ldap2ldap connector, the objectClass values of the destination directory are taken from the source objetc constructor. So the generated entry cannot be added to destination directory.

I try to use syncoptions in lsc.properties without success.

A workaround is to edit source object (for example src/imp/java/org/lsc/inetOrgPerson.java) and modify the constructor.

History

Updated by Clément Oudot over 1 year ago

A little update from myself:

using syncoptions works! You can set the objectClass value with:

lsc.syncoptions.user = org.lsc.beans.syncoptions.PropertiesBasedSyncOptions
lsc.syncoptions.user.default.action = F
lsc.syncoptions.user.objectClass.force_value = "user"

Updated by Clément Oudot over 1 year ago

To be more precise, you have to set in force_value all the destination objectClasses, else LSC will try to update target objectClasses, for example :

lsc.syncoptions.user.objectClass.force_value = "top";"user";"person";"organizationalPerson"

Updated by Jonathan Clarke 10 months ago

  • Status changed from New to Closed
  • Target version set to 1.2.0
  • % Done changed from 0 to 100

This is no longer the case in 1.2 branch. Closing.

Please note it is now always necessary to define objectClass values to create.

Also available in: Atom PDF