OIDC plugin ignores the standard "locale" claim when provisioning new accounts

Summary The OIDC authentication plugin does not read the standard locale claim from the ID token or userinfo response when provisioning a new account. As a result, new users signing in via OIDC always get the workspace's fallback language instead of the language indicated by their identity provider, even when locale is present and correctly formatted. Current behavior Our IdP (Keycloak) sends a valid OIDC ID token with the standard locale claim set to pt-BR, e.g. (decoded payload, trimmed): Despite this, a brand new account created through our OIDC provider signs in with the interface language set to English (US), not Português (Brasil). Looking at plugins/oidc/server/auth/oidcRouter.ts, the object passed to accountProvisioner only forwards name, email, emailVerified, and avatarUrl: Neither profile.locale nor token.locale is ever read, so the claim is silently discarded regardless of what the identity provider sends. Expected behavior The…