[mitreid-connect] Authorization Request Language/i18n

[Justin Richer]

You'd need to send a query parameter and have a resolver set up to look for this parameter. The locale resolver is used with every interactive request including the authorization page. 


--Justin
 Sent from my phone
-------- Original message --------From: Thomas Meyer <thomas at m3y3r.de> Date: 4/13/18  11:52 AM  (GMT-05:00) To: Justin Richer <jricher at mit.edu> Subject: Re: [mitreid-connect] Authorization Request Language/i18n 
Hi,
Mhh okay, given a JavaScript app that uses implicit flow and in this app he user did already choose language de how to pass this via the authorization code request. Where to add a query parameter or header field? Is this possible?
Is the resovler also involved in this initial oauth request?
MfgThomas
Am 13.04.2018 5:31 nachm. schrieb Justin Richer <jricher at mit.edu>:
The current implementation uses a locale resolver that’s tied to the system configuration, so there’s a single language for the entire site. If you want it to be configured per-user or by some other metric, you need to override the resolver defined by the class ConfigurationBeanLocaleResolver. This bean is wired by up locale-config.xml. I’d recommend that whatever you use fall back to the included resolver as default, for consistency.
 — Justin

On Apr 13, 2018, at 11:11 AM, Thomas Meyer <thomas at m3y3r.de> wrote:
Hi,
Did I miss it or is there no mechanism in the oauth/OpenIDConnect standard to pass a eventually available language setting to the MitreID Connect server so an already set language can also be used in the login and consent page.
Any hints how to solve this?
With kind regardsThomas_______________________________________________
mitreid-connect mailing list
mitreid-connect at mit.edu
http://mailman.mit.edu/mailman/listinfo/mitreid-connect


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/mitreid-connect/attachments/20180413/9b857c1a/attachment.html