Le 11/06/2018 à 17:15, Lior Dotan a écrit : > On Mon, Jun 11, 2018 at 5:11 PM Clément OUDOT <[email protected]> > wrote: >> >> >> Le 11/06/2018 à 16:01, Lior Dotan a écrit : >> >> You are correct of course but I did try with (objectClass=*) at first >> and I got the same error, which is why I tried to change the filter. >> In the past using async and (objectClass=*) worked okay. >> >> >> You can still try different values for referral setting in connection: >> >> referral: mandatory, one of the following values: IGNORE, THROUGH, THROW or >> ERROR. Most of the time you should either IGNORE them, go THROUGH or handle >> them as an ERROR > With THROUGH & ERROR I got the following error: > org.lsc.exception.LscConfigurationException: Configuration exception: > java.lang.IllegalArgumentException: Illegal value for > java.naming.referral property. > > With THROW I get the same errors as above. > _________________________________________________
I don't see any other solution than switching to ldapSourceService. -- Clément Oudot | Identity Solutions Manager [email protected] Worteks | https://www.worteks.com _______________________________________________________________ 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
