5:31 p.m.
You'd probably want to support multiple concurrent themes for different
languages (french, spanish, english, etc...). I'm just not sure how the
user-agent's language would be discovered. Some do it by hostname i.e.
www.google.es or by a URL pattern example.com/en-US/...
Just something to think about.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
5:12 a.m.
Not sure why you'd want multiple themes?
Internationalization will be taken care of by locale specific message bundles (e.g.
messages_no.properties). We could also add the option of having locale specific templates
(e.g. login_no.ftl), not sure that would be needed though.
I'm not sure how correct locale is discovered either, I'm sure there's folks
on the portal theme that knows this ;). We may need to add an option to pass it as a query
param from the app though. With the hostname examples you've given wouldn't those
be app urls rather than keycloak urls?
For example:
www.myapp.co.uk -> keycloak.org/auth/rest/realm/myrealm?client_id=...&locale=en_UK
www.myapp.no -> keycloak.org/auth/rest/realm/myrealm?client_id=...&locale=no
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 4 February, 2014 11:31:52 PM
Subject: [keycloak-dev] theme thought
You'd probably want to support multiple concurrent themes for different
languages (french, spanish, english, etc...). I'm just not sure how the
user-agent's language would be discovered. Some do it by hostname i.e.
www.google.es or by a URL pattern example.com/en-US/...
Just something to think about.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
7:01 a.m.
On 2/5/2014 6:12 AM, Stian Thorgersen wrote:
Not sure why you'd want multiple themes?
Different apps may want a different logon screens?
Internationalization will be taken care of by locale specific message
bundles (e.g. messages_no.properties). We could also add the option of having locale
specific templates (e.g. login_no.ftl), not sure that would be needed though.
message bundles work great for logging messages. I'm not sure its
always the case for rendered content. I've also been told in the past
that different cultures prefer different color schemes.
I don't know what the right answer is, but its something that should be
researched for best practice.
I'm not sure how correct locale is discovered either, I'm
sure there's folks on the portal theme that knows this ;). We may need to add an
option to pass it as a query param from the app though. With the hostname examples
you've given wouldn't those be app urls rather than keycloak urls?
Answering my own question: Openid Connect supports locale as a query param.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
7:52 a.m.
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Wednesday, 5 February, 2014 1:01:42 PM
Subject: Re: [keycloak-dev] theme thought
On 2/5/2014 6:12 AM, Stian Thorgersen wrote:
> Not sure why you'd want multiple themes?
>
Different apps may want a different logon screens?
As you login to a SSO realm, and not an individual app, shouldn't it be the same?
> Internationalization will be taken care of by locale specific message
> bundles (e.g. messages_no.properties). We could also add the option of
> having locale specific templates (e.g. login_no.ftl), not sure that would
> be needed though.
>
message bundles work great for logging messages. I'm not sure its
always the case for rendered content. I've also been told in the past
that different cultures prefer different color schemes.
True, so you may need local specific stylesheets as well
I don't know what the right answer is, but its something that should be
researched for best practice.
Yup, that's the main reason I've not included internationalization support now ;)
> I'm not sure how correct locale is discovered either, I'm sure there's
> folks on the portal theme that knows this ;). We may need to add an option
> to pass it as a query param from the app though. With the hostname
> examples you've given wouldn't those be app urls rather than keycloak
> urls?
>
Answering my own question: Openid Connect supports locale as a query param.
Seems like every time when I propose to add a query param to the login url, OpenID connect
has done the same ;)
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11:19 a.m.
On 2/4/2014 6:31 PM, Bill Burke wrote:
You'd probably want to support multiple concurrent themes for
different
languages (french, spanish, english, etc...). I'm just not sure how the
user-agent's language would be discovered. Some do it by hostname i.e.
www.google.es or by a URL pattern example.com/en-US/...
The accept-language http
header can be a good starting point.
I'd like to see preferred and accepted locales be a setting in the
user's profile. That way, a federated application can find out that
information at login and pick the appropriate locale for the app's user
session.
Just something to think about.
3977
days inactive
3978
days old
4 comments
3 participants
participants (3)
-
Bill Burke -
ssilvert＠redhat.com -
Stian Thorgersen