[keycloak-dev] Internationalization support (KEYCLOAK-301)

[Bill Burke]

What's the best practice for choosing local?

* User-Agent header?
* From a login hint?  I think OIDC has something like this (but what 
about SAML)?
* Should we store this information somewhere (cookie, 
UserModel.attribute, etc..)


On 2/23/2015 11:53 AM, Michael Gerber wrote:
> Hi all,
>
> I started to work on the internationalization support
> (https://issues.jboss.org/browse/KEYCLOAK-301).
>
> I’ve already implemented the realm config in the admin console. I’ve put
> it into the „Theme Setting“ (see screenshot)
> I added the possibility to enable internationalization, add supported
> locales and a select a default locale.
>
> Now I’d like to implement the logic which choose the correct locale.
> Therefore I need the http header, cookie, query parameter, realm and user.
> The LoginFormsProvider and AccountProvider have all this information
> apart from the http header and the cookie.
> So I thought I could replace the UriInfo with the HttpRequest, but that
> doesn’t work, because I can not access the UriInfo through the
> HttpRequest (java.lang.NoSuchMethodError:
> org.jboss.resteasy.spi.HttpRequest.getUri()Ljavax/ws/rs/core/UriInfo;).
> So, I will add the HttpHeader to the LoginFormsProvider
> and AccountProvider, or does anyone have a better idea?
>
> @Bill
> How do you plan to store the claim „locale“ on a user? Will it be
> accessible through the UserModel interface?
>
> Best
> Michael
>
>
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com