Hello, this could be a bug, you should fill an issue on https://github.com/lsc-project/lsc/issues
Clément. Le sam. 1 juin 2019 à 21:24, Ralf Mattes <[email protected]> a écrit : > > Hello list, > > I just moved a sync setup to our production server and encounter a strange > error. LSC complains about > "Your baseDn settings (ou=Personen,o=Hochschule für Musik,l=Freiburg,c=de) > does not end with the LDAP naming context (o=Hochschule f?r > Musik,l=Freiburg,c=de)." > Note the diffence in the organization part. The locale is set to > 'en_US.UTF-8' (but changing this doesn't seem to make a difference). What > magic switch/configuration option did I miss to get the LDAP naming context > reported from the server interpreted in the correct encoding (the server > _does_ report the correct naming context - it works in Python, PHP, Perl ...). > > TIA Ralf Mattes > > > > _______________________________________________________________ > 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 _______________________________________________________________ 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
