The IDP items on the OAuth config details page aren't properly enabled for translation. They will always show up as English. See the code here: https://github.com/spadgett/console/blob/ded0de8063bec2e02a07defeb1a050f4c9bf0399/frontend/public/components/cluster-settings/oauth.tsx#L50-L89 `{{label}}` will always evaluate to the English value set in the map from just above.
ralpert The IDP menu items are missing translation for other languages. Could you please help to get the translation file updated?
Created attachment 1791596 [details] ja translation file
Hey @cajieh - Sorry I missed this yesterday. I think the issue here is that even though we're generating keys with the comments (//t('public~Request Header') and so on), we don't actually internationalize the values in the application. We're just passing these hard-coded English values in. Sometimes the translators will prefer to leave proper nouns like Google in English, but I can see that they did translate a few of the terms. With the way the code is now, we won't ever seem those.
Checked on ocp 4.9 cluster with payload 4.9.0-0.nightly-2021-06-22-193627, now the add idp menu are translated in Chinese/Japanese/Korean, but "OpenID Connect" string in menu and on adding page are not translated in Japanese. Will we add the translation for it?
Hey @yanpzhan - It looks like Aiko intentionally left that in English.
@ralpert Thanks for responding to the query.
@yanpzhan - Please retest this fix.
According to Comment 8, the "OpenID Connect" string is intentionally kept in English, there is no other doubts about the fix, so move the bug to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759