FileNet P8 Application Engine, Version 5.2.1       Application server:  WebSphere Application Server     

Configuring Lightweight Third Party Authentication (LTPA)

To set up LTPA security, configure settings to match on both the Content Platform Engine application server and the Application Engine application server. If your Application Engine and Content Platform Engine are on the same WebSphere® Application Server, you are not required to configure LTPA.

About this task

High availabilityNote: If your environment uses Workplace XT, follow the instructions for configuring Light weight Third Party Authentication (LTPA) in the IBM FileNet Workplace XT 1.1.5 installation and upgrade.
High availabilityImportant: In a highly available WebSphere environment where Content Platform Engine and Application Engine are managed by different deployment managers, perform any LTPA configuration steps on the administrative server only. The scope of this action will affect the entire application server configuration.

If you are already using LTPA with your Content Platform Engine application server, you must export only the existing keys and copy the key file to the Application Engine server. Check with your Content Platform Engine administrator.

To configure LTPA:

Procedure

  1. On the Content Platform Engine server, log in to the WebSphere administrative console.
  2. Navigate to the LTPA settings page at Security > Global security and select LTPA from the right side of the panel.
  3. Enter a value for the LTPA timeout that is larger than the default. For example, if the timeout value is left at the default value of 120 minutes, the LTPA key expires after 2 hours. Users will not be able to log in to Workplace after being logged in for 2 hours.
    High availabilityImportant: In high availability environments, set the timeout value for forwarded credentials between servers:
    Option Description
    WebSphere Application Server 7.0 60000
  4. Save your changes.
  5. In the box for Cross-cell single sign-on, type a password to create the LTPA password.

    For password restrictions, see the WebSphere Application Server documentation. If you have already configured Content Platform Engine for LTPA, use the existing password in the Application Engine configuration.

  6. Enter the fully qualified path for the Key File Name. For example, /opt/LTPA/ltpa_key_name.
  7. Click Export keys. Verify that a message like the following message is displayed: The keys were successfully exported to the file ltpa_key_name.
  8. Click OK, then click Save changes directly to the master configuration.
  9. Stop and restart the WebSphere Application Server instance.
  10. Copy the key file from the Content Platform Engine server location you specified to a directory on the Application Engine server. For example, /opt/LTPA/ltpa_key_name
  11. On the Application Engine server, log in to the WebSphere administrative console.
  12. Navigate to the LTPA settings page at Security > Global security and select LTPA from the right side of the panel.
  13. Enter a value for the LTPA timeout that is larger than the default. For example, if the timeout value is left at the default value of 120 minutes, the LTPA key expires after 2 hours. Users will not be able to log in to Workplace after being logged in for 2 hours.
    High availabilityNote: In high availability environments, set the timeout to 60,000.
  14. Save your changes.
  15. In the box for Cross-cell single sign-on, type and confirm the LTPA password you created for Content Platform Engine.

    For password restrictions, see the WebSphere Application Server documentation. If you have already configured Content Platform Engine for LTPA, use the existing password in the Application Engine configuration.

  16. Specify the path for the key file that you copied to the Application Engine server. For example, /opt/LTPA/ltpa_key_name.
  17. Click Import keys. Verify that a message like the following one is displayed: The keys were successfully imported from the file ltpa_key_name.
  18. Save your changes.

    High availabilityIn a highly available environment, synchronize the changes across all nodes after saving your configuration settings.



Last updated: March 2016
p8pin205.htm

© Copyright IBM Corporation 2013, 2016.