[keycloak-dev] KEYCLOAK-3210 Temporary Fix

Hynek Mlnarik hmlnarik at redhat.com
Wed Mar 21 07:59:02 EDT 2018


Hi,

could you please submit a pull-request?

Thanks

--Hynek

On Tue, Mar 20, 2018 at 3:48 AM, Donald Gay <donaldquixote at gmail.com> wrote:

> 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
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>



-- 

--Hynek


More information about the keycloak-dev mailing list