It's strange that no one else has reported this. We had several people report the issue with umlats, but no one else seems to have the issue with the database encoding. Maybe there's something different with your database config? Could you try with a default MySQL database installation and see if you can reproduce the issue? Also, can you give me a sample name that shows the problems.

I added a test for umlats to registration and account management, see https://github.com/keycloak/keycloak/pull/3036. Once it's in I'll schedule a run with CI, which tests with a range of different databases.

On 12 July 2016 at 16:13, Igor Zuk <igor.zuk@qualitytaskforce.com> wrote:

Thank you for a quick response.

 

I’m using 1.9.2.Final and the problem is a bit different, it’s not limited to registration screen.

 

I’m saying, that ISO-8859-1 is the default encoding, because all the text columns in USER_ENTITY table had encoding latin1. The table was created completely by Keycloak as the database was empty in the beginning. I manually switched encoding of FIRST_NAME to UTF-8 and modified it so it contained special letters. I started the user editor in Keycloak admin console and this name was displayed correctly. I added a single character to it, saved, and then the name got messed up with question marks instead of all special characters.

 

From: Stian Thorgersen [mailto:sthorger@redhat.com]
Sent: Tuesday, July 12, 2016 3:43 PM
To: Stian Thorgersen <stian@redhat.com>
Cc: Igor Zuk <igor.zuk@qualitytaskforce.com>; keycloak-user@lists.jboss.org
Subject: Re: [keycloak-user] Keycloak user data encoding

 

By the way this was fixed in 1.6.0.Final, see https://issues.jboss.org/browse/KEYCLOAK-1830?jql=project%20%3D%20KEYCLOAK%20AND%20text%20~%20%22encoding%22

 

Are you using an old version?

 

On 12 July 2016 at 15:37, Stian Thorgersen <sthorger@redhat.com> wrote:

Why are you saying the default encoding is ISO-8859-1? All forms are encoded as UTF-8 and all strings passed to the database should be UTF-8 encoded as well.

 

The only thing that is ISO-8859-1 is the message properties, but those are converted to UTF-8 when added to HTML pages.

 

On 12 July 2016 at 14:58, Igor Zuk <igor.zuk@qualitytaskforce.com> wrote:

Hi

 

I have an encoding problem. By default users' data fields (e.g. first name and last name) are encoded using ISO-8859-1. People from many countries can't properly create accounts as their personal data is silently messed up. How can I fix it?

·         The MySQL DB receives already damaged names. By default all columns are ISO-8859-1-encoded, but manually converting them to UTF-8 doesn't help.

·         Manual account modification from admin console has same effect.

·         Change of default server (Wildfly) encoding to UTF-8 doesn't do anything.

 

Best regards

Igor Żuk

 

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user