Use this page to specify the shared keys and configure the authentication mechanism that is used to exchange information between servers. You can also use this page to specify the amount of time that the authentication information remains valid and specify the single sign-on configuration.
- Click .
- Under Authentication, click LTPA.
- Click .
- Under Available realm definitions, verify that the appropriate registry is configured.
- Click Apply. When security is enabled and any of these properties change, return to the Global security panel and click Apply to validate the changes.
Key set group
Specifies groups of public, private, and shared keys. These key groups enable the application server to manage multiple sets of Lightweight Third Party Authentication (LTPA) keys.
Specifies whether to generate a new set of LTPA keys in the configured keystore, and to update the runtime with the new keys. By default, LTPA keys are regenerated on a schedule every 90 days, configurable to the day of the week.
Each new set of LTPA keys is stored in the keystore associated with the key set group. A maximum number of keys (or even one) can be configured. However, it is recommended to have at least two keys; the old keys can be used for validation while the new keys are being distributed.
This step is not necessary during security enablement. A default set of keys is created during the first server startup. If any nodes are down during a key generation event, the nodes should be synchronized with the Deployment Manager before restart.
LTPA timeout value for forwarded credentials between servers
Specifies the period of time during which the server credentials from another server are valid. After this time period expires, the server credential from the other server must be revalidated.
Specify a value for this field that is greater than the value specified for the Cache timeout field on the Authentication cache settings panel.
|Units||Minutes and seconds|
In version 220.127.116.11 and earlier, an integer between 5 and 153722867280911
An integer between 5 and 5265000. The maximum timeout value is 5256000 minutes, the equivalent of 10 years.
Enter a password which will be used to encrypt and decrypt the LTPA keys from the SSO properties file. During import, this password should match the password used to export the keys at another LTPA server (for example, another application server Cell, Lotus® Domino® Server, and so on). During export, remember this password in order to provide it during the import operation.
After the keys are generated or imported, they are used to encrypt and decrypt the LTPA token. Whenever the password is changed, a new set of LTPA keys are automatically generated when you click OK or Apply. The new set of keys is used after the configuration changes are saved.
Specifies the confirmed password that is used to encrypt and decrypt the LTPA keys.
Use this password when importing these keys into other application server administrative domain configurations and when configuring SSO for a Lotus Domino server.
Fully qualified key file name
Specifies the name of the file that is used when importing or exporting keys.
Enter a fully qualified key file name, and click Import Keys or Export Keys.
Specifies whether the server imports new LTPA keys.
- Enter the appropriate password in the Password and Confirm password fields.
- Enter the directory location where the LTPA keys are located in the Fully qualified key file name field prior to clicking Import Keys.
- Do not click OK or Apply, but save the settings.
Specifies whether the server exports LTPA keys.
To support single sign-on (SSO) in the WebSphere® product across multiple application server domains (cells), share the LTPA keys and the password among the domains. Use the Export Keys option to export the LTPA keys to other domains.
To export the LTPA keys, make sure that the system is running with security enabled and is using LTPA. Enter the file name in the Fully qualified key file name field and click Export Keys. The encrypted keys are stored in the specified file.
com.ibm.websphere.ltpa.Realmproperty. The realm setting, by default, is always the global or administrative realm. If you are using multiple security domains and want the key file to represent an application in one of these multiple security domains, you need to manually update this key file property with the correct multiple security domain realm prior to supplying the keyfile to these products.