Repository navigation
Replies: 1 comment
|
I think it has historic reasons why With the introduction of the OIDC specific endpoints the query param you have to go for is see #47369 (comment) OIDC Endpoint Examples Registration Page (prompt=create) Login Page Reset Password Page |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I noticed what seems to be a locale handling inconsistency (possibly a bug) with
kc_localein Keycloak authorization flows.When triggering an authentication flow from OIDC Debugger using:
kc_locale=<locale>in the initial authorization request query params, the first login/authenticator page still loads in English. It looks like
LocaleUtil.processLocaleParam()is not being triggered during the initial request.However, if the URL is modified later during the flow (for example on the 2nd authenticator page), the locale gets applied correctly and the UI switches to the expected language.
From debugging, I noticed:
buildRegister()explicitly calls:LocaleUtil.processLocaleParam(...)buildAuthorizationCodeAuthorizationResponse()does not.So during the normal OIDC authorization code flow, the locale parameter seems to be ignored on the first render.
Has anyone faced this before?
Is this expected behavior, or could this be a bug/inconsistency in locale initialization during the authorization flow?
Thanks!
All reactions