Re: [keycloak-dev] Locale cookie vs ui_locales priority
The way at least it was supposed to work was that the Locale cookie would
only be set if a user has explicitly changed the locale. That way we can
remember a users preference even when the user is logged out.
Are you seeing ui_locales not taking affect without a user having used the
locale drop-down?
On Mon, 13 Aug 2018 at 23:42, Johannes Knutsen <johannes(a)kodet.no> wrote:
Currently the LocaleHelper#getUserLocale chooses locale priority
based
on the following order:
1. kc_locale query parameter
2. Locale cookie
3. User profile
4. ui_locales query parameter
5. Accept-Language http header
We are building clients which uses the ui_locales parameter to select
localization of the login to match the locale of the client.
Since the locale cookie has a higher priority than the ui_locales
query parameter, the ui_locales query parameter is ignored for any
auth requests with a kc_locale cookie present.
1. Do you see any implications of prioritizing the ui_locales
parameter above the locale cookie when resolving locale?
2. Are there reasons why the ui_locales does not update the locale
cookie value the same way kc_locale parameter does it?
Best regards,
Johannes Knutsen
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev