We have an issue where attributes that eDir has decided to base64 encode
prevents object synchronization from IDM to Active Directory and
OpenLDAP. The can be caused by something as simple as a trailing space
in user updatable attributes (which we should be handling in our
applications) to accented / foreign characters.

I'm looking for strategies as to how to handle this. Should we pass all
outbound events destined for AD and OpenLDAP through stylesheets
changing "Rene" to "Ren\\c3\\a9e"? Are there settings in the drivers
to strip / convert special characters on their own? Ideas?


liamr's Profile: https://forums.netiq.com/member.php?userid=1044
View this thread: https://forums.netiq.com/showthread.php?t=53225