You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How does localization of client.name/client.description work?
#14495
I noticed the other day that in the KC admin panel client.name and client.description support localized values.
I'm not sure how localization around these fields work - to be honest I'm not sure that there is anywhere in the default UI that would resolve + display the localized text. Is localization just something that could be opted into on the frontend if desired?
My main concern is that I am interested in making this client metadata something that clients integrating with keycloak can configure, and I would like to make sure that they cannot specify something here that could get them/others into trouble (in particular I would not want them to be able to inject or otherwise abuse this functionality).
I've considered preventing ${} as a safeguard to prevent these fields from being "localized" entirely. Would greatly appreciate thoughts + insight here. Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I noticed the other day that in the KC admin panel client.name and client.description support localized values.
I'm not sure how localization around these fields work - to be honest I'm not sure that there is anywhere in the default UI that would resolve + display the localized text. Is localization just something that could be opted into on the frontend if desired?
My main concern is that I am interested in making this client metadata something that clients integrating with keycloak can configure, and I would like to make sure that they cannot specify something here that could get them/others into trouble (in particular I would not want them to be able to inject or otherwise abuse this functionality).
I've considered preventing
${}as a safeguard to prevent these fields from being "localized" entirely. Would greatly appreciate thoughts + insight here. Thanks!All reactions