2012/7/25 David Coutadeur <[email protected]>: > > Hi everybody, > > I noticed a weird behaviour in the last release of lsc-2.0. > > 1/ when using a logback.xml with all levels at "INFO", I got nothing > synchronized... It stays blocked with no special message. > Note : I use ldap async source service, with a sunDS. > Note: logback.xml is shown below, with all INFO values replaced by DEBUG >
What is the bug: changing the loglevel do affect the synchronization? Or do the async LDAP source service never work with SunDS? I only tested it with OpenLDAP, so it is possible that the SunDS specific code do not work. > 2/ This one is more a comment than a bug : > when moving from lsc1.0 to lsc2.0 : > - with a ldapsourceservice, no problem > - with an async ldap source service, binary attributes does not seem to > be synchronized the same way. Indeed, attribute : > <string>userCertificate;binary</string> as shown below must be replaced by : > <string>userCertificate</string> > > Maybe the job to get the binary attribute is done in internal ? Certainly, but I can't confirm it. > Once it is done, you must also take care to the Delimiter, else, the > userCertificate could be splitted into two certificate. > Maybe these points can be added to the documentation ? > Yes: http://lsc-project.org/wiki/documentation/2.0/upgrade-from-1.2 Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
