Again and again we receive enquiries about multi-language support for Citrix Gateway and AAA. Why is quickly explained: A portal theme is often created, ideally with RfWebUI, in order to customise the look to the customer's requirements. A login scheme is often used to fulfil security requirements. If the field labelling is to be adapted here, as in the following example, this results in unsightly behaviour.
It should look like this:
![](https://image.jimcdn.com/app/cms/image/transf/dimension=480x10000:format=png/path/s62d7b78f02af0221/image/i344807ad61596a51/version/1718742916/image.png)
However, it has the wrong language and field labelling:
![](https://image.jimcdn.com/app/cms/image/transf/dimension=510x10000:format=png/path/s62d7b78f02af0221/image/i834b8d2287a3ab57/version/1718742916/image.png)
Of course, a custom login schema.xml was created with the appropriate labelling in the corresponding languages.
How did this issue come about?
Unfortunately, even with Release 14.1, it is still not possible to use a custom portal theme and custom login schema with multi-language support in parallel. This can lead to confusion, as this combination can be configured via the GUI, but does not work during processing.
This is because field labels for custom login schemes are stored in:
/var/netscaler/logon/LogonPoint/custom/strings.en.json
while field labels for custom portal themes are read from
/var/netscaler/logon/themes/<custom_theme_name>/strings.en.json
The bold marking differentiates here according to localisation, e.g. en for English and de for German.
Solution:
After creating the customised portal themes and login schema, last one is localised. The easiest way to do this is via GUI as described here for the Custom_DualAuth.xml which was customised for German via "Edit". This is then selected via "Select" for the schema.
![](https://image.jimcdn.com/app/cms/image/transf/dimension=940x10000:format=png/path/s62d7b78f02af0221/image/i4712109b084e9ac5/version/1718742916/image.png)
The custom label for the schema is then copied from
"/var/netscaler/logon/LogonPoint/custom/strings.en.json" nach "/var/netscaler/logon/themes/<custom_theme_name>/strings.en.json".
The strings.de.json file then looks like this, for example:
![](https://image.jimcdn.com/app/cms/image/transf/dimension=940x10000:format=png/path/s62d7b78f02af0221/image/idc176a64ae52c821/version/1718742916/image.png)
The assignment via the tag "custom_dualauth" followed by the field "passcode" is clearly recognisable here!
Let's wait and see what the future holds. Unfortunately, this procedure is still necessary in 2024 to provide multi-language support.
Kommentar schreiben