Customizing non-UI-related text elements in the Loginapp REST API

To customize text elements, a set of empty language property files can be either created for all or for specific instances. Text elements in these language property files are used for non-UI-related texts (such as email, SMS, or Cronto texts that are not shown in the browser, etc.).

Initial setup

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

Copy resource keys from the original language property files

After creating empty language property files, copy the required template texts from the original strings_*.properties files. Use resource keys (i.e. including the template text.

Do not make changes to 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.

  1. Copy texts from the original template files:
  2. In the IAM installation folder, go to:
  3. Use a text editor to open the corresponding language file, e.g. to customize English texts.
  4. Find and copy the desired existing element by searching for its key (e.g.
  5. Paste the copied line into the corresponding empty string-property file and adapt the copied wording as required.
  6. The changes are applied automatically after 30 seconds.

Adding a new language

  1. Adding new languages requires:
  2. Adding a new string_*.properties with the 2-letter country code.
  3. Adding the new language in the Config Editor under Loginapp >> Language Settings in the list of Valid Languages.
  4. Note that depending on the used feature set, there may be other points in the configuration where the new language must be added (e.g. language choice in user registration self-service or user management in the Adminapp).