I am doing some custom data validation when replicating from AD to OpenLDAP using LSC. I have some JavaScript that performs auxiliary searches in both the source and target directories. I've recently noticed various search filter errors in my lsc.out file and have discovered it is the unfortunate result of new AD data that contains special characters which need escaped when used in a search filter. It appears as though the ScriptableJndiServices methods that accept a filter object do not do the required escaping. Am I expected to do this myself before calling the methods or should I expect the methods to do this for me and open a bug report/feature request? The examples I can readily reproduce involve data containing parenthesis and the search method which generates an unbalanced parenthesis error. I have not tested the other methods or reviewed the specific source but assume this is not restricted to the search method.
-Jon C. Kidder American Electric Power Middleware Services Email: [email protected]<mailto:[email protected]> Phone: 614-716-4970
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
