Configure the client for LTPA token authentication: collecting the authentication method information

 

+

Search Tips   |   Advanced Search

 

Overview

Use this task to configure LTPA token authentication. Do not configure the client for LTPA token authentication unless the authentication mechanism configured in WAS is LTPA. When a client authenticates to a WebSphere Application Server, the credential created contains an LTPA token. When a Web service calls a downstream Web service, one can configure the first Web service to send the LTPA token from the originating client. Do not attempt to configure LTPA from a pure client. LTPA works only when you configure the client-side of a Web service acting as a client to a downstream Web service. In order for the downstream Web service to validate the LTPA token, the LTPA keys on both servers must be the same.

Complete the following steps to specify how to collect the LTPA token authentication information:

 

Procedure

  1. Launch an assembly tool.

  2. Click...

    Windows | Open perspective | Other | J2EE | Application Client Projects | appname | appClientModule | META-INF | application-client.xml (right-click) | Open with | Deployment descriptor editor

  3. Click the WS Bindings tab, which is located at the bottom of the deployment descriptor editor within the assembly tool.

  4. Expand the Security request sender binding configuration > Login binding section.

  5. Click Edit to view the login binding information and select LTPA.  If LTPA is not already there, enter it as an option. The login binding dialog is displayed. Select or enter the following information:

    Authentication method

    Specifies the type of authentication that occurs. Select LTPA to use identity assertion.

    Token value type URI and token value type local name

    When you select LTPA, edit the token value type URI and the local name fields. Specifies values for custom authentication types, which are authentication methods not mentioned in the specification.  For the token value type URI field, enter the following string: http://www.ibm.com/websphere/appserver/tokentype/5.0.2.  For the local name field, enter the following string:  LTPA.

    Callback handler

    Specifies the JAAS callback handler implementation for collecting the LTPA information. Specify the implementation...

    com.ibm.wsspi.wssecurity.auth.callback.LTPATokenCallbackHandler

    Basic authentication user ID and basic authentication password

    For LTPA, one can leave these fields empty. However, when you omit this information, the LTPA CallbackHandler implementation attempts to obtain the LTPA token from the invocation (RunAs) credential. If an invocation (RunAs) credential does not exist, then the LTPA token is not propagated.

    Property name and property value

    For LTPA, one can leave these fields empty.

 

What to do next

See Configuring the client for LTPA token authentication: specifying LTPA token authentication if you have not previously specified this information.

 

See Also


Lightweight Third Party Authentication

 

Related Tasks


Configure the client for LTPA token authentication: specifying LTPA token authentication
Configure the client security bindings using an assembly tool
Configure the security bindings on a server acting as a client using the administrative console