Hi Clement, Yes, you are welcome to open issues and, if you can, fix them !
Regarding the audits / security nodes, they may be optional and the parser needs to be less strict (one more issue :) Regarding the PDU message, it seems to be an incomplete LDAP message usage sent by Apache Directory API. That's probably because you are using the asynchronous source service which seems to throw away some search responses with having exhausted the data sent by the source directory (another issue). Regarding the asynchronous way of launching LSC, I have through to write a lscd script to wrap the lsc command line when launched with "-a" flag but still need to do it. If you wrap the service in such script, you are welcome to contribute it ! Regards, -- Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ Le 4 avril 2012 15:46, Clément OUDOT <[email protected]> a écrit : > Le 4 avril 2012 15:32, Sébastien Bahloul <[email protected]> a > écrit : > > Hi Clement, > > > > 1. You are right CFG_DIR seems to be never used ! > > 2. lsc-agent is command line tool to interact with an already started > > instance of asynchronous LSC. Command line options should not be the > same, > > I'll need to check that issue. > > 3. I agree that "Starting LSC" should be reserved for a synchronization. > > Should be fixed also. > > Ok, do you want me to open issues on Redmine? I think that I can patch > the first one, by forcing the -f option if it was not given in command > line. > > > > > > Regarding your extra question: lsc.xml does not support any include > > directive, but it can include several tasks. So it is possible to define > > /etc/lsc subdirectories to keep track of one task per lsc.xml file (i.e. > > subdirectory) or one global file with the overall settings. In a single > > lsc.xml file, the only shared settings are logging and security settings. > > Thanks for this answer, it is clear to me. > > I just tested this new version to create on small connector that will > synchronize passwords on the fly between OpenLDAP and SUN. It is > working great but I have some questions (again!): > > * I first made a configuration without any audits or security > paragraphs, but this is not valid. I adda an audit paragraph with a > csv audit part configured to false, and this works. But for me we > should be able to omit the audits part in a configuration file. Note > that I did not have to include the security part. > > -> reported error: > [org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of > element 'lsc' is not complete. One of > '{"http://lsc-project.org/XSD/lsc-core-2.0.xsd":audits, > "http://lsc-project.org/XSD/lsc-core-2.0.xsd":security}' is expected.] > > * I use the async LDAP provider, and get plenty of WARN messages: > > avr. 04 15:42:43 - WARN - The PDU has been fully decoded but there > are still bytes in the buffer. > > Do you know why? My LDAP source is OpenLDAP 2.4.30. > > * By default, launching lsc with -a do not detach the command from the > console. Is there a way to run it as a daemon (except to launch the > command with a &) > > > Clément. >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
