Thanks Clement. You are making my day. Thanks for spending your time in this great project.
Now last question for today. I have only LDAP enabled right now. So I wasn't setting the password as I think in AD I can only do it if I use LDAPS. The users are being created suspended. Although I added: <dataset> <name>userAccountControl</name> <policy>KEEP</policy> <createValues> <string>AD.userAccountControlSet( "0", [AD.UAC_SET_NORMAL_ACCOUNT])</string> </createValues> </dataset> It is still created like disabled user (546 value). Is this an AD problem (I need to set up the password too) or I am misconfiguring it? Kind regards. On 29 October 2012 14:02, Clément OUDOT <[email protected]> wrote: > 2012/10/29 Emilio García <[email protected]>: > > Hi, > > > > Sorry for not being detailed enough. Now it works, I mean it creates the > > users. They appear suspended but I presume because I didn't populate the > > userAccountControl properly. > > > > But having said that the tool never ends running. It gets stuck. It maybe > > because this machine has very little memory... > > > > Here is the log: > > > > Oct 29 13:05:31 - DEBUG - Loading XML configuration from: > > C:\Users\Administrator > > \Downloads\lsc-core-2.0.1-dist\lsc-2.0.1\bin\..\etc\lsc.xml > > Oct 29 13:05:31 - INFO - Reflections took 250 ms to scan 1 urls, > producing > > 60 k > > eys and 226 values > > Oct 29 13:05:32 - DEBUG - Importing XML schema file: > > schemas/lsc-core-2.0.xsd > > Oct 29 13:05:32 - INFO - Logging configuration successfully loaded from > > C:\User > > > s\Administrator\Downloads\lsc-core-2.0.1-dist\lsc-2.0.1\bin\..\etc\logback.xml > > Oct 29 13:05:32 - INFO - LSC configuration successfully loaded from > > C:\Users\Ad > > ministrator\Downloads\lsc-core-2.0.1-dist\lsc-2.0.1\bin\..\etc\ > > Oct 29 13:05:32 - INFO - Connecting to LDAP server > > ldap://10.226.114.161:389/dc > > =test,dc=local as [email protected] > > Oct 29 13:05:32 - WARN - Your baseDn settings > (OU=IDVault,DC=test,DC=local) > > doe > > s not end with the LDAP naming context (dc=test,dc=local). This is > probably > > an e > > rror ! For LSC 1.X users, this is part of the changelog to 2.X. > > Oct 29 13:05:32 - INFO - Connecting to LDAP server > > ldap://10.234.214.142:389/dc > > =openldap,dc=local as cn=admin,dc=openldap,dc=local > > Oct 29 13:05:32 - INFO - Starting async for Users > > Oct 29 13:05:33 - INFO - # Adding new object CN=Emilio > > Garcia,OU=IDVault,DC=tes > > t,DC=local for Users > > dn: CN=Emilio Garcia,OU=IDVault,DC=test,DC=local > > changetype: add > > samAccountName: Emilio Garcia > > sn: Garcia > > cn: Emilio Garcia > > description: GARCIA ([email protected]) > > objectClass: inetOrgPerson > > > > Oct 29 13:05:33 - INFO - # Adding new object CN=Gillian > > Seed,OU=IDVault,DC=test > > ,DC=local for Users > > dn: CN=Gillian Seed,OU=IDVault,DC=test,DC=local > > changetype: add > > samAccountName: Gillian Seed > > sn: Seed > > cn: Gillian Seed > > description: SEED ([email protected]) > > objectClass: inetOrgPerson > > > > It gets stuck forever at this point... if I use -a but it works fine if I > > use -s. > > > Some explanation on command line options here: > http://lsc-project.org/wiki/documentation/2.0/execution/start > > If you use the async mode, your connector will stay tuned to your > source base waiting for modifications. It allows you to synchronize > data on the fly. To make it working with your configuration, you need > to configure asyncLdapSourceService instead of ldapSourceService, and > activate syncprov overlay in OpenLDAP. > > If you want a simple batch synchronization, just use your current > configuration and the -s option. > > > Clément. > -- Cloudreach Limited is a limited company registered in England with registered number 06975407 The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved. This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let us know that it has gone to the wrong person.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
