first, sorry for my former post. didn't get the digest right. As of lately I had a look into lsc's connection module ibatis and found it is outdated by about two years. At least I did not find a hint for a more modern implementation. (configurable charset, for example?)
Maybe I'm wrong and simply looked up the wrong website (found the last commit in october/2018: typo) I am going to introduce an authentication system to a company sized >2000 employees and need an interface from ldap to any kind of SQL db to integrate complicated administrative detours into a to-be-developed tool. You might understand I do not want to set my bets on a dead horse, and I need some confidence in it's future. I found lsc not only the sole serious solution on the web, but nonetheless extremely valuable and convenient for its job. The more I was disappointed of the aging interfaces and the low rate of recent development. I wonder how I should address our need to interface a central ldap instance (-> global village syndrome) for access to a subset of <300 objects to administer locally. Either use an lsc job to fetch necessary data or let someone develop a SOAP/XML interface (accompanied by several dozens of hurdles of needless privacy restrictions, getting engaged in endless debates). Better not to interfere with international managers and just get the job done with some reliable backdoor account. But such a decision needs tools with a promising future. What would you do if you were in my shoes?
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
