> Hi Sebastien, > > I finally came around to try this today and it didn't work. It threw an error > that seemed like this value is empty. Any other suggestions? > > Thanks! > Marian > > Quoting Sébastien Bahloul <[email protected]>: > >> Hi Marian, >> >> Try with entryDN attribute. >> >> Regards >> Le 24 nov. 2014 09:23, "Marian Harbach" <[email protected]> a >> écrit : >> >> Hi, >> >> thanks for your answer. I tried that and wanted to choose the dn as the >> pivot, as there are no other unique attributes for OUs (the ou name itself >> may occur in multiple branches). However that does not seem to work. Is >> there a trick to do that? >> >> Thanks! >> Marian >> >> On 24. Nov 2014, at 09:15, Sébastien Bahloul <[email protected]> >> wrote: >> >> Hi Marian, >> >> You should create a task specifically to handle the OU structure: create >> the various subou before trying to sync objects in them. >> >> Regards, >> Le 24 nov. 2014 09:00, "Marian Harbach" <[email protected]> a >> écrit : >> >>> Hi list, >>> >>> we are currently trying to use LSC to populate a Metadirectory (i.e. an >>> empty OpenLDAP that only contains a basic tree structure) with contents >>> from several other LDAPs. In principle I got this to work easily, but now I >>> am stuck with a problem regarding sub-OUs. >>> >>> For example, lets assume I want to copy everything (which is really >>> inetOrgPersons and organisationalUnits) from LDAP1 under >>> ou=org1,dc=University,dc=de to the meta-ldap at ou=orgA,dc=meta. Right now >>> LSC just collects all inetOrgPersons from LDAP1 and adds them to the meta. >>> However, there is some structure in LDAP1, so that there is >>> ou=suborg1,ou=org1,dc=University,dc=de and >>> ou=suborg2,ou=org1,dc=University,dc=de. This is currently ignored during >>> the copying process. I would like to maintain this sub-OU structure in the >>> meta so that there is ou=suborg1,ou=orgA,dc=meta and >>> ou=suborg2,ou=orgA,dc=meta with the corresponding persons underneath. This >>> could also extend to an arbitrary number of levels of depth (i.e. >>> subsubsubsuborgX). Is there a way to do this with LSC 2.1.1? I saw an >>> example in the old documentation for LSC 1.x but didn’t find any >>> corresponding options in the LSC 2.x docs. >>> >>> Thank you for your help! >>> >>> Best, >>> Marian >>> >>> >>> _______________________________________________________________ >>> Ldap Synchronization Connector (LSC) - http://lsc-project.org >>> >>> lsc-users mailing list >>> [email protected] >>> http://lists.lsc-project.org/listinfo/lsc-users >> -- >> Marian Harbach >> Research Associate >> Distributed Computing and Security Group >> Leibniz Universität Hannover >> Schloßwender Str. 5, 30159 Hannover, Germany >> Tel. +49 (0) 511 762 79 9038 > > >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
