[keycloak-dev] KEYCLOAK-3210 Temporary Fix

[Donald Gay]

We want to use Keycloak on MSSQL, but have concerns with the timeline of
proposed fix for https://issues.jboss.org/browse/KEYCLOAK-3210 since it
requires significant schema changes.

One commenter noted that

*"Using Hibernate's native annotation @Nationalized for JPA fields might
help here - left for further investigation."*

We have run some initial tests using @Nationalized on all fields specified
in documentation as supporting unicode characters, and along with
setting sendStringParametersAsUnicode=false,
this seems to resolve the issue while not impacting unicode support.

Any thoughts on implementing this to provide quicker resolution? From my
perspective it seems like a desirable change to make regardless of any
other efforts to clean up schemas.

Thanks