Joost Sannen

The login schema of OnlyUsername.xml differs between 13.1 and 14.1 . I couldn't get the label translation working with the default one in 13.1 . GOAL Change 'User name' to 'Username :' and in Dutch 'Gebruikersnaam :'Remove the assistive text in the username box.Change ' Please enter UserName ...' to 'Enter your credentials for [NAME OF SERVICE] and in Dutch 'Voer uw account in voor toegang tot [NAME OF SERVICE]'What I did is Use the OnlyUsername.xml from 14.1 on my 13.1 production Netscaler.Removed all values in strings.en.json and strings.nl.json in /var/netscaler/logon/LogonPoint/custom/Edited strings.en.json and strings.nl.json in my custom theme located /var/netscaler/logon/themes/[THEME NAME]/Warning: If you don't get immediate proper results this might be the internal Netscaler caching. Even when the integrated caching feature is not enabled. Invalidate objects of the loginstaticobjects content group by flushing objects. Reopen an InPrivate browser and try again. My json files strings.en.json { "onlyusername_user_name":"Username :", "onlyusername_please_enter_username_...":"Enter your credentials for [NAME OF SERVICE]", "onlyusername_please_supply_either_username_as_saamaccountname":"" } strings.nl.json { "onlyusername_user_name":"Gebruikersnaam :", "onlyusername_please_supply_either_username_as_saamaccountname":"", "onlyusername_please_enter_username_...":"Voer uw account in voor toegang tot [NAME OF SERVICE]" } @Hemang Raval​ this may need some improvement in Netscaler. Regards, Joost

@Hemang Raval​ . Well, in the end I couldn't get it fully functional on a new Netscaler 14.1 . The GUI is buggy. When you try to update language labels of an existing login schema it states that the language file couldn't be modified. But behind that there's another notification. It appears all label modifications you'll do in the gui changes the specific language json files in /var/netscaler/logon/LogonPoint/custom/ . But I did find a solution. I follow up shortly.

@Hemang Raval​ ​ , it does function on a fresh 14.1 box. So, that's great. It appears that some labels in my production box are wrong. I'll fix this but it has to wait to next year. Best wishes! Regards, Joost

@Hemang Raval​ , I know the options but it still doesn't work for me on 13.1-50.23 . I'll do another attempt in my sandbox environment with the latest 14.1 version. @Fernando Avelino​ , great article! I'm aware of some of the possibilities. When the sandbox environment does not function too I'll try to use the mentioned techniques in this article.

Hi Hemang, Thank you for answering. Yes, we want to provide our Access Gateway in Dutch and English. This doesn't work unfortunately. Let me try this once more in the latest 13.1 build. I'll report back. Best regards, Joost

Hi, after a support case and asking around in the field I have 2 problems left in translating my Gateway portal theme based on RfWebUI. I can translate all applicable fields except User namePlease supply either username as saamaccountnameI'm using nFactor based on OnlyUsername.xml. I can force 1 language so momentarily 'Please supply either username as saamaccountname' is empty. How to translate it properly?