Issue #790 has been reported by Armando Martins. ---------------------------------------- Bug #790: Binary attribute is not well written in destination LDAP octetstring attribute http://tools.lsc-project.org/issues/790
Author: Armando Martins Status: New Priority: High Assigned to: Clément OUDOT Category: Core Target version: Problem in version: When LSC add the user for the first time he write the attribute like this : binarysid:: AQUAAAAAAAUVAAAA77+9OzJ577+9Ve+/vVEdA2pm77+977+9AAA= But on the next execution ha can't find the user because the filter don't match the attribute. If now i take the attribute from my active directory and write it to the destination attribute with ldapmodify. LSC works fine because the filter match the attribute. So it seems there is a bug with the transformation of binary attributes from source to destination. Link to the thread in the mailing list : http://lists.lsc-project.org/pipermail/lsc-users/2015-September/002690.html -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
