Le 11/04/2016 11:40, Gustavo Castelo a écrit :
Hi,
I've run into an issue where the
LscModifications.getModificationsByHash converts the attribute name to
lower case, probably to avoid duplicate attribute names where case is
the only difference. But if I have a destination service that does
care about the casing this creates a problem since I loose the true
attribute names and values, i.e. LDAP memberOf is converted to memberof.
The workaround is to have my own method that creates this mapping,
however, would it make sense to introduce a method that keeps the
attribute case?
Hello,
you are right, this was one because in LDAP, attributes name are not
case sensitive. This can be a problem if destination is not an LDAP
directory. I see no simple solution for this, you should open an issue
in the tracker so we can see how to make this configurable:
http://tools.lsc-project.org/projects/lsc/roadmap
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
87, rue de Turbigo - 75003 PARIS
Blog: http://sflx.ca/coudot
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev
