Hello

I need to synchronize one attribute from AD to openldap

there is a error running the task

juin 28 11:09:58 - ERROR - Error while adding entry
uid=proca,ou=people,dc=int,dc=fr in directory
:javax.naming.directory.SchemaViolationException: [LDAP: error code 65 -
no objectClass attribute]; remaining name 'uid=proca,ou=people'
juin 28 11:09:58 - ERROR - Error while synchronizing ID
uid=proca,ou=people,dc=int,dc=fr: java.lang.Exception: Technical problem
while applying modifications to the destination
# Fri Jun 28 11:09:58 GMT+01:00 2019
dn: uid=proca,ou=people,dc=int,dc=fr
changetype: add
employeenumber: 04133

I guess there's something wrong in the mainIdentifier ?

<mainIdentifier>js:"uid=" +
javax.naming.ldap.Rdn.escapeValue(srcBean.getDatasetFirstValueById("samaccountname"))
+ ",ou=people,dc=int,dc=fr"</mainIdentifier>

SRC pivot is

<pivotAttributes>
          <string>samaccountname</string>
        </pivotAttributes>

DST is

 <pivotAttributes>
          <string>uid</string>
        </pivotAttributes>


could it be the source of my pb ?

is there a way to set the mainIdentifier to the dst DN ? from list of
methods in https://lsc-project.org/javadoc/2.1-SNAPSHOT/ I see all
methods related to DN are deprecated :

example |getFullDistinguishedName
<https://lsc-project.org/javadoc/2.1-SNAPSHOT/org/lsc/beans/LscBean.html#getFullDistinguishedName-->()|

|
|

I was expecting to use dstBean.|getFullDistinguishedName
<https://lsc-project.org/javadoc/2.1-SNAPSHOT/org/lsc/beans/LscBean.html#getFullDistinguishedName-->()|

good or bad idea ?

thanks .


PS : I also have :

 <defaultPolicy>FORCE</defaultPolicy>
        <conditions>
          <create>true</create>
          <update>true</update>
          <delete>true</delete>
          <changeId>false</changeId>
        </conditions>

_______________________________________________________________
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

Reply via email to