From eb4f741ca6278fbfc1db094c0579559cee1b4330 Mon Sep 17 00:00:00 2001 From: Mikkel Christensen Date: Wed, 8 Oct 2025 12:40:05 +0200 Subject: [PATCH] Added note about the lack of language control via the Accept-Language HTTP header for FTN flows. --- src/pages/verify/guides/choose-language.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/pages/verify/guides/choose-language.mdx b/src/pages/verify/guides/choose-language.mdx index a808e7b2..480f3cef 100644 --- a/src/pages/verify/guides/choose-language.mdx +++ b/src/pages/verify/guides/choose-language.mdx @@ -8,6 +8,14 @@ subtitle: How to specify the language used by the user interface (where supporte By default, Criipto Verify uses the _Accept-Language_ HTTP request header to figure out which language the user prefers. + + +**Note** that this is not supported for [Finnish Trust Network](/verify/e-ids/finnish-trust-network/) logins. + +Here, one _must_ use the `ui_locales` parameter in the [signed request object](/verify/e-ids/finnish-trust-network/#authentication-request-signing). + + + You can override this per authentication request by specifying a `ui_locales` query parameter. This works for both OpenID Connect and WS-Federation, even if WS-Federation does not have protocol support for per-request language selection. The actual support for controlling the language varies by eID method