Configure the client for response decryption: decrypting the message parts

Important distinction between Version 5.x and Version 6 applications

Note: The information in this article supports version 5.x applications only that are used with WebSphere Application Server Version 6. The information does not apply to version 6 applications. Prior to completing these steps, read either of the following topics to become familiar with the WS Extensions tab and the WS Binding tab in the Client Deployment Descriptor Editor within an assembly tool:

• Configuring the client security bindings using an assembly tool

• Configuring the security bindings on a server acting as a client using the administrative console

These two tabs are used to configure the Web services security extensions and the Web services security bindings, respectively.

Complete the following steps to specify which response message parts to decrypt when configuring the client for response decryption. The server response encryption and client response decryption configurations must match.

1. Launch an assembly tool. For more information on the assembly tools, see Assembly tools.

2. Open the J2EE perspective by clicking Window > Open perspective > Other > 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 Extensions tab, which is located at the bottom of the deployment descriptor editor within the assembly tool.

6. Expand the Response receiver configuration > Required confidentiality section.

7. Select the parts of the message that decrypt by clicking Add and selecting either Bodycontent or Usernametoken. The following information describes these message parts:

   Bodycontent

   The user data portion of the message.

   Usernametoken

   The basic authentication information, if selected.

   The information selected in this step is encrypted by the server in the response sender.

   Important: A username token is typically not sent in the response. Thus, you usually do not need to select username token.

What to do next

Related concepts
XML encryption

Related tasks
Configuring the client for response decryption: choosing a decryption method
Configuring the client security bindings using an assembly tool
Configuring the security bindings on a server acting as a client using the administrative console
Configuring key locators using an assembly tool
Configuring key locators using the administrative console