To configure the client for response decryption, specify
which response message parts to decrypt when configuring the client.
The server response encryption and client response decryption configurations
must match.
Before you begin
Important: There is an important
distinction between Version 5.x and Version 6 and later applications.
The information in this article supports Version 5.x applications
only that are used with WebSphere® Application Server
Version 6.0.x and later. The information does not apply to
Version 6.0.x and later 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:
These two tabs are used to configure the Web services
security extensions and the Web services security bindings, respectively.
About this task
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.
Procedure
- Launch an assembly tool. For more information,
see the related information on Assembly Tools.
- Switch to the Java™ Platform,
Enterprise Edition (Java EE)
perspective. Click Window > Open Perspective > J2EE.
- Click Application Client Projects > application_name >
appClientModule > META-INF.
- Right-click the application-client.xml file, select Open
with > Deployment descriptor editor.
- Click the WS Extensions tab, which is located at
the bottom of the deployment descriptor editor within the assembly
tool.
- Expand the Response receiver configuration >
Required confidentiality section.
- Select the parts of the message that you must 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.