Configuring Lightweight Third Party Authentication

You can configure Lightweight Third Party Authentication (LTPA) by using LTPA profiles. An LTPA profile specifies the key that is used for authentication across servers within the same domain name system. The LTPA profile must be associated with a security profile, and the security profile must be associated with an endpoint.

Before you can configure an LTPA profile, you must have an LTPA key. You can export an LTPA key from servers such as WebSphere® Application Server. For more information about LTPA, see Lightweight Third Party Authentication (LTPA).

Note: WebSphere Application Server can periodically generate key sets. This option must be disabled, or must be monitored for key generation events. If the key is regenerated, a new LTPA key file must be exported from WebSphere Application Server. Then, the Eclipse Amlen LTPA profile must be updated with the new key file.
When you create an LTPA profile, you must specify the following components:
  • Name
    Specifies the name that identifies the LTPA profile.
    The name must not have leading or trailing spaces and cannot contain control characters, commas, double quotation marks, backslashes, or equal signs. The first character must not be a number or any of the following special characters:

    ! # $ % & ' ( ) * + - . / : ; < > ? @

  • Key Filename
    Specifies the name of the file that contains the LTPA key.
  • Password
    Specifies the password that is associated with the LTPA key.

For more information about configuring LTPA profiles by using the Amlen WebUI, see Configuring LTPA profiles by using the Amlen WebUI.

For more information about configuring LTPA profiles by using REST Administration APIs, see Creating and updating an LTPA profile by using REST Administration APIs.