Le 19/06/2019 à 11:12, Jehan Procaccia a écrit :
> Hello,
>
> I run a LSC task with success from ldap (SRC = openldap not supann
> enabled) to another ldap (DST = supann enabled => + supannPerson and
> supannCMS objectClass) . My problem is with interpretation of the
> Functionality matrix :
>
> https://lsc-project.org/documentation/2.0/configuration/syncoptions
>
> If I set defaultPolicy to FORCE and for objecClass the policy FORCE
> with <forceValues>, my objectClass are correctly pushed as stated in
> lsc.xml , but they are replaced at every task runs although it is
> already there :
>
> changetype: modify
> replace: objectClass
> objectClass: supannCMS
> objectClass: supannPerson
> objectClass: inetOrgPerson
> objectClass: labeledUriObject
> objectClass: eduPerson
> objectClass: fdPersonalInfo
> objectClass: organizationalPerson
> objectClass: posixAccount
> objectClass: sambaSamAccount
> objectClass: shadowAccount
> objectClass: person
> objectClass: top
>
> here is my lsc.xml section regarding objecClass
>
>   <defaultPolicy>FORCE</defaultPolicy>
>         <conditions>
>           <create>true</create>
>           <update>true</update>
>           <delete>true</delete>
>           <changeId>true</changeId>
>         </conditions>
>         <dataset>
>           <name>objectclass</name>
>           <policy>FORCE</policy>
>           <forceValues>
>             <string>"supannCMS"</string>
>             <string>"supannPerson"</string>
>             <string>"inetOrgPerson"</string>
>             <string>"labeledUriObject"</string>
>             <string>"eduPerson"</string>
>             <string>"fdPersonalInfo"</string>
>             <string>"organizationalPerson"</string>
>             <string>"posixAccount"</string>
>             <string>"sambaSamAccount"</string>
>             <string>"shadowAccount"</string>
>             <string>"person"</string>
>             <string>"top"</string>
>           </forceValues>
>         </dataset>
>
>
> with KEEP policy it does not add those objectClass .


Hello Jehan,

for objectClass, the best is to use KEEP with createValues:


        <dataset>
          <name>objectclass</name>
          <policy>KEEP</policy>
          <createValues>
            <string>"inetOrgPerson"</string>
            <string>"organizationalPerson"</string>
            <string>"person"</string>
            <string>"top"</string>
          </createValues>
        </dataset>

So the object classes will be added at entry creation and not updated
after that.



-- 
Clément Oudot | Identity Solutions Manager

[email protected]

Worteks | https://www.worteks.com

_______________________________________________________________
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