Customizing text elements in the Loginapp (JSP)

  • Initial setup
  • For all instances:
    Create the files strings_de.propertiesstrings_en.properties (and so on) to directory ./instances/common/loginapp-texts/
  • For one specific instance:
    Create the files strings_de.propertiesstrings_en.properties (and so on) to directory ./instances/<instance-name>/loginapp-texts/
  1. Language templates
  2. In the IAM installation folder open app/loginapp/WEB-INF/classes/strings_*.properties (* choose the correct language code).
  3. Find the desired existing text via search (e.g. "Login failed").
  4. Copy the line into the newly created string-property file from "Initial setup" and adapt the copied wording as required.
  5. Do not make changes in the original strings_*.properties file.

  6. The changes are applied automatically after 30 seconds.

Example

To change the login page input field label from "Username" to "Contract-No.", store the file strings_en.properties 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 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).