<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">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 <strong class="final-path">ConfigurationBeanLocaleResolver. </strong><span class="final-path">This bean is wired by up </span><strong class="final-path">locale-config.xml</strong>. I’d recommend that whatever you use fall back to the included resolver as default, for consistency.<div class=""><b class=""><br class=""></b></div><div class=""> — Justin<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 13, 2018, at 11:11 AM, Thomas Meyer <<a href="mailto:thomas@m3y3r.de" class="">thomas@m3y3r.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Hi,<div dir="auto" class=""><br class=""></div><div dir="auto" class="">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.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Any hints how to solve this?</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">With kind regards</div><div dir="auto" class="">Thomas</div></div>_______________________________________________<br class="">mitreid-connect mailing list<br class=""><a href="mailto:mitreid-connect@mit.edu" class="">mitreid-connect@mit.edu</a><br class="">http://mailman.mit.edu/mailman/listinfo/mitreid-connect<br class=""></div></blockquote></div><br class=""></div></body></html>