Merci beaucoup Clément!
I'll encounter this problem only on the DIT synchrnization task, so there
are very few attributes I can handle.
Tried the integration of the entryDN pivot attribute, but LSC seems not to
find any source object. As I get as many errors as there are entries, the
culprint id the getOneFilter line.
So, How can I hoandle the "entryDN" parameter?
- I tried <string>dn</string> in <pivotAttributes>, as well as
<string>entryDN</string>
- In addition, in getOneFilter: <![CDATA[(&(dn={dn}))]]> or
<![CDATA[(&(dn={entryDN}))]]>
Without gaining any positive results.
Bon après-midi!
Patrice
2016-02-03 11:56 GMT+01:00 Clément OUDOT <[email protected]
>:
>
>
> Le 03/02/2016 11:09, Patrice M. a écrit :
>
> Hello from Paris! (Pour les français, vous pouvez répondre en français :) )
>
> I'm new here, so trying to chat around.
>
> I subscribed to this list mainly to get some help with filters into the
> lsc.xml file.
> Actually,
>
> I have to build an LDAP server replica using LDAP Synchronization
> Connector. LSC, to add some intelligence regarding the destination usage.
>
> I'm experiencing a troubling problem while synchronizing the DIT, as in
> the source directory, child branches of same name can appear.
>
> *DIT*:
>
> <dc=root>
> |_ <dc=subroot>
> |_ <dc=entity1>
> |_ <dc=entity2>
> |_ <dc=entity3>
> |_<dc=child_branch1>
> |_<dc=TOTO>
> |_<dc=child_branch2>
> |_<dc=TOTO>
> |_ <dc=entityN>
>
> *The problem is:* the child branches can appear anytime, and correspond
> to a specific application usage. Every child branch can contain the same
> sub "dc".
>
> *My question is:* how can I set LSC to properly synchronize this DIT
> structure type?
>
> The <baseDn> parameter is set to dc=subroot,dc=root. The actual
> <getOneFilter> is set to
> <![CDATA[(&(dc={dc})(objectClass=OrganizationalUnit)]]>
>
> Now, LSC doens't synchronize any dc=TOTO, and returns a
> javax.naming.SizeLimitExceededException:
> Too many entries returned [...] exception.
>
> Thanks a lot by advance for any kind of help you can provide?
>
>
>
> Hello Patrice,
>
> you can try to find another pivot attribute that can be added to dc and
> used in the filter like :
>
> <![CDATA[(&(dc={dc})(cn={cn})(objectClass=OrganizationalUnit)]]>
>
>
> If source and destination use the same namingContext, you can also try to
> use the DN (entryDN) as pivot attribute.
>
>
>
> --
> Clément OUDOT
> Consultant en logiciels libres, Expert infrastructure et sécurité
> Savoir-faire Linux
> 87, rue de Turbigo - 75003 PARIS
>
>
> _______________________________________________________________
> Ldap Synchronization Connector (LSC) - http://lsc-project.org
>
> lsc-users mailing list
> [email protected]
> http://lists.lsc-project.org/listinfo/lsc-users
>
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
