General task options

This section describes available options to configure a LSC task. You should replace TASKNAME by a task name specified in the global configuration option lsc.tasks.

The full name of the JAVA class to use for plain LDAP object. For example, for person, you could use org.lsc.objects.inetOrgPerson. Be careful that this class has to exist in this instance of LSC.

The full name of the JAVA BEAN class to use for specialisation of the synchronization. For example, for person, you could use org.lsc.beans.inetOrgPersonBean. Be careful that this class has to exist in this instance of LSC.

The synchronisation type for this task between the two defined services. Available options are ldap2ldap and db2ldap.

You can specify conditions for the 4 actions create, update, delete and modrdn. These conditions are written in JavaScript.

For example :

lsc.tasks.TASKNAME.condition.create = 1 > 0
lsc.tasks.TASKNAME.condition.update =
srcBean.getAttr('updateTimeStamp') > dstBean.getAttr('updateTimeStamp')
lsc.tasks.TASKNAME.condition.delete = false
lsc.tasks.TASKNAME.condition.modrdn = false

In the condition create you have access to the srcBean.

In the condition update you have access to the srcBean and dstBean.

In the condition delete you have access to the srcBean.

In the condition modrdn you have access to the srcBean and dstBean.

You can set the dn of the object in the configuration. You can use Javascript and you have access to the srcBean.

Example:

lsc.tasks.TASKNAME.dn = 'cn=' + srcBean.getAttributeValueById('uid')

Note: To never change the DN, set this property to ”” (the empty string). In this case, LSC will ignore MODRDN operations. This will also stop LSC from creating objects, since they have no DN.