Hi Clement, Hugh, The builtin LDAP source service is effectively not designed to handle such use case. But it is possible to write a source service that will respect the LDAP hierarchy to send results in the correct order.
Are you planning to run it on a periodical basis ? If so, we can preload the whole directory, sort entries thanks to a LDAP hierarchical sort class and manage the entries with that order. Regards, -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ Le 24 avril 2012 18:15, Clément OUDOT <[email protected]> a écrit : > Le 24 avril 2012 18:07, Hugh Kelley <[email protected]> a écrit : > > I am trying to use LSC to essentially "mirror" a very hierarchical (many > > nested OUs) production LDAP instance into an isolated pre-production LDAP > > instance. My current issue is that the updates are being generated in > > reverse (or perhaps random) order, so that child objects creations are > > attempted before parent objects have been created. > > > > See the bottom of this post for an excerpt from my LDIF. I know there > is a > > <sortedBy> option I can use at the connection level, but I don't know of > any > > LDAP attribute that could be used in a sort-by-depth manner. Are there > any > > clever solutions for this? > > > > One ideaI am exploring is to sort by whenChanged, thinking that the > > most-recently changed objects should be the children. However, this > > lsc.xml configuration appears to be invalid. > > > > </ldapConnection> > > . . . . . . > > <binaryAttributes> > > <string>objectGUID</string> > > </binaryAttributes> > > <sortedBy>whenChanged</sortedBy> > > </ldapConnection> > > > > ERROR - org.lsc.exception.LscConfigurationException: > > javax.xml.bind.UnmarshalException > > - with linked exception: > > [org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content > was > > found starting with element 'sortedBy'. No child element is expected at > this > > point.] > > org.lsc.exception.LscConfigurationException: > > javax.xml.bind.UnmarshalException > > > > > sortedBy option does not work in 2.0. An issue has been opened for the > next version: http://tools.lsc-project.org/issues/440 > > > LSC is not a very good tool to synchronize a hierarchical tree, just > for the reason you mention in your mail: entries are get in a non > hierarchical order. Maybe someone in this list has done such > synchronization and can help us? > > > Clément. > _______________________________________________________________ > 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
