Customizing text elements
17.4.10. Customizing UI-related and non-UI-related text elements

Initial setup

To customize text elements, a set of empty language property files can be either created as common language files or for specific instances.

Changes in these language property files are related to Loginapp (JSP) UI texts and non-UI-related texts (such as email, SMS, or Cronto texts that are not shown in the Loginapp) for both, the Loginapp (JSP) and Loginapp REST UI use case.

  • Create empty property files:
  • .
    For all instances:
    Create the files (and so on) to directory ./instances/common/loginapp-texts/
  • .
    For one specific instance:
    Create the files (and so on) to directory ./instances/<instance-name>/loginapp-texts/

Language template texts

After creating empty language property files, copy the required parts from the original strings_*.properties files.

  • Copy texts from the original template files:
  • 1.
    In the IAM installation folder, go to:
  • 2.
    Use a text editor to open the corresponding language file, e.g. to customize English texts.
  • 3.
    Find and copy the desired existing text via search, e.g. "Login failed".
  • 4.
    Paste the copied line into the corresponding empty string-property file and adapt the copied wording as required.
  • Do not make changes in the original strings_*.properties file, i.e. do not make any changes to the original template files as these files will be overwritten without notice during updating and installation procedures.

  • The changes are applied automatically after 30 seconds.


To change the login page input field label from "Username" to "Contract-No.", store the file with the contents

loginpage.username = Contract-No.

to directory ./instances/common/loginapp-texts/.

Adding a new language

The following steps are required to add a new language to the JSP-Loginapp:

  • Add string property file: to common instance or specific instance (e.g. for the loginapp to ./instances/common/loginapp-texts/ or ./instances/<instance-name>/loginapp-texts/ (create the directory if it doesn't exist))
  • Add as valid language: Using the ConfigEditor, add the new language as a valid language (Loginapp >> Language Settings)
  • Adapt Webpages: If the user can change the display language on the pages of the loginapp: Adapt the links (usually part of the sub-page header.jsp). See 17.4.11. Customizing UI (look and feel) of the JSP-Loginapp on how to proceed with this and how to activate the changes.

To test, you can call any page using the HTTP GET parameter lang=xx (where "xx" is the two-letter ISO language code).