Adding an LTPA provider to the Physical view

To test a web service that requires Lightweight Third-Party Authentication message-level authentication, you must enter details about the LTPA provider and the level of authentication required. To add a LTPA provider to the Physical view of the Architecture School perspective, use the General menu.

Lightweight Third-Party Authentication (LTPA) is an authentication technology used in IBM® WebSphere® and Lotus® Domino® products.

Click General > LTPA Provider to enter details about a server that acts as an LTPA provider for a web service that you want to test and that requires LTPA message-level authentication.

The LTPA Provider window is displayed.

The following table describes the fields, lists, and check boxes on the LTPA Provider window.

Table 1. Fields that define an LTPA provider
Field Type Description
Host Mandatory The host name or IP address of the server.
Port Mandatory The relevant port number of the server.
Path Mandatory if the server root is not protected The URL path of the server.
LTPA Cookie Name Mandatory The default name of the LTPA cookie.
Note: The value entered here must match the name of the cookie configured on the server.
Realm Optional The realm contains the name of the authenticating host and indicates the group of users who might have access, for example, registered_users@example.com.
LTPA Version Mandatory Web services security supports both LTPA Version 1 and LTPA Version 2 (LTPA2) tokens.
Note: LTPA2 tokens are more secure than LTPA tokens.

You need to determine which LTPA version is used by the server and select that version in the list.

Use SSL Mandatory if required by the server Select this check box to enable security for the transport. Selecting the check box makes the other SSL controls on the page available.
Server certificates to trust Conditional
All available identity stores are displayed in the drop-down menu. Select one of the following menu items:
Trust All
To accept any certificate presented by the server, regardless of its validity. This option is the default, and assumes that you are focused on testing an application rather than the security of the server.
New
To define a new identity store. See Identity stores and SSL.
Identity store
To specify an identity store that contains certificates that the client is to trust.
Client identities to give to server Conditional
All available identity stores are displayed in the menu. If you use mutual authentication, a suitable identity is selected from the chosen identity store. Select one of the following menu items:
None
If the server does not request an identity.
New
To define a new identity store. See Identity stores and SSL.
Identity store
To specify an identity store that contains certificates that the server is to trust.
Feedback