Configure the client for identity assertion: collecting the authentication method

We can configure identity assertion authentication. The purpose of identity assertion is to assert the authenticated identity of the originating client from a web service to a downstream web service.

This task is used to configure identity assertion authentication. The purpose of identity assertion is to assert the authenticated identity of the originating client from a web service to a downstream web service. Do not attempt to configure identity assertion from a pure client. Identity assertion works only when we configure on the client-side of a web service acting as a client to a downstream web service.

In order for the downstream web service to accept the identity of the originating client (just the user name), supply a special trusted BasicAuth credential that the downstream web service trusts and can authenticate successfully. Specify the user ID of the special BasicAuth credential in a trusted ID evaluator on the downstream web service configuration. See the information on trusted ID evaluators.

Complete the following steps to specify how the client collects the authentication information:

Tasks

1. Launch an assembly tool. For more information, see the related information on Assembly Tools.
2. Switch to the Java EE perspective. Click Window > Open Perspective > J2EE.

3. Click Application Client Projects > application_name > appClientModule > META-INF.
4. Right-click the application-client.xml file, select Open with > Deployment descriptor editor.

5. Click the WS Binding tab, which is located at the end of the Deployment Descriptor Editor within an assembly tool.

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

7. Click Edit to view the login binding information and select IDAssertion. The login binding dialog is displayed. Select or enter the following information:

   Authentication method

   The authentication method specifies the type of authentication that occurs. Select IDAssertion to use identity assertion.

   Token value type URI and Token value type Local name

   When we select IDAssertion, we cannot edit the token value type Universal Resource Identifier (URI) and the local name. Specifies custom authentication types. For IDAssertion authentication, leave these values blank.

   Callback handler

   JAAS callback handler implementation for collecting the BasicAuth information. Specify the com.ibm.wsspi.wssecurity.auth.callback.NonPromptCallbackHandler implementation for IDAssertion.

   Basic authentication User ID and Basic authentication Password

   In this field, the trust mode entered in the extensions is BasicAuth. Trusted user ID and password in these fields. The user ID specified must be an ID that is trusted by the downstream web service. The web service trusts the user ID if it is entered as a trusted ID in a trusted ID evaluator in the downstream web service bindings. If the trust mode entered in the extensions is Signature, we do not need to specify any information in this field.

   Property name and Property value

   Specifies properties with name and value pairs, for use by custom callback handlers. For IDAssertion, we do not need to specify any information in this field.

What to do next

To use the identity assertion authentication method, we must specify the method in the Security extensions section of an assembly tool. See Configure the client for identity assertion: specifying the method if we have not previously specified this information.

Related:

Trusted ID evaluator

Development and assembly tools

Configure the client for identity assertion: specifying the method

Configure the client security bindings using an assembly tool