Configure the client for request signing: digitally signing message parts
To configure the client for request signing, specify which message parts to digitally sign when configuring the client.
There is an important distinction between Version 5.x and V6 and later applications. The information in this article supports V5.x applications only that are used with WebSphere Application Server V6.0.x and later. The information does not apply to V6.0.x and later applications. Prior to completing these steps, read either of the following topics to become familiar with the Security Extensions tab and the Port Binding tab in the Web Services Client Editor within an assembly tool.
- Configure the client security bindings using an assembly tool
- Configure the security bindings on a server acting as a client using the console
These two tabs are used to configure the Web services security extensions and the Web services security bindings, respectively.
Overview
Complete the following steps to specify which message parts to digitally sign when configuring the client for request signing:
Procedure
- Launch an assembly tool. For more information on the assembly tools, see Assembly tools
- Click Windows > Open perspective > Other > J2EE.
- Click Application Client projects > application > appClientModule > META-INF
- Right-click the application-client.xml file, select Open with > Deployment Descriptor Editor, and click the WS Extension tab. The Client Deployment Descriptor is displayed.
- Expand Request sender configuration > Integrity. Integrity refers to digital signature while confidentiality refers to encryption. Integrity decreases the risk of data modification while the data is transmitted across the Internet. For more information on digitally signing SOAP messages, see XML digital signature.
- Indicate which parts of the message to sign by clicking Add and selecting body, timestamp, or SecurityToken. The following list contains descriptions of the message parts
- body
- The body is the user data portion of the message.
- timestamp
- The time stamp determines if the message is valid based on the time that the message is sent and then received. If timestamp is selected, proceed to the next step and select Add created time stamp to add a time stamp to a message.
- SecurityToken
- The security token authenticates the client. If this option is selected, the message is signed.
You can choose to digitally sign the message using a time stamp if Add created time stamp is selected and configured. You can digitally sign the message using a security token if a login configuration authentication method is selected.
- Optional: Expand the Add created time stamp section and select this option if you want a time stamp added to the message. You can specify an expiration time for the time stamp, which helps defend against replay attacks. The lexical representation for duration is the [ISO 8601] extended format PnYnMnDTnHnMnS, where:
- nY represents the number of years
- nM represents the number of months
- nD represents the number of days
- T is the date and time separator
- nH represents the number of hours
- nM represents the number of minutes
- nS represents the number of seconds. The number of seconds can include decimal digits to arbitrary precision.
For example, to indicate a duration of 1 year, 2 months, 3 days, 10 hours, and 30 minutes, the format is: P1Y2M3DT10H30M. Typically, you configure a message time stamp for about 10 to 30 minutes, for example, 10 minutes is represented as: P0Y0M0DT0H10M0S. The P character precedes time and date values.
Results
If you configure the client and server signing information correctly, but receive a Soap body not signed error when executing the client, you might need to configure the actor. You can configure the actor in the following locations on the client in the Web Services Client Editor within an assembly tool:
- Click Security extensions > Client service configuration details and indicate the actor information in the Actor URI field.
- Click Security extensions > Request sender configuration > Details and indicate the actor information in the Actor field.
You must configure the same actor strings for the Web service on the server, which processes the request and sends the response back. Configure the actor in the following locations in the Web Services Editor within the WebSphere Application Server Toolkit:
- Click Security extensions > Server service configuration.
- Click Security extensions > Response sender service configuration details > Details and indicate the actor information in the Actor field.
The actor information on both the client and server must refer to the same exact string. When the Actor fields on the client and server match, the request or response is acted upon instead of being forwarded downstream. The Actor fields might be different when you have Web services acting as a gateway to other Web services. However, in all other cases, make sure that the actor information matches on the client and server. When Web services are acting as a gateway and they do not have the same actor configured as the request passing through the gateway, Web services do not process the message from a client. Instead, these Web services send the request downstream. The downstream process that contains the correct actor string processes the request. The same situation occurs for the response. Therefore, it is important that you verify that the appropriate client and server Actor fields are synchronized.
What to do next
After you have specified which message parts to digitally sign, specify which method is used to digitally sign the message. See Configure the client for request signing: choosing the digital signature method for more information.
XML digital signature
Request sender
Request receiver
Security token
Related tasks
Configure the client security bindings using an assembly tool
Configure the client for request signing: choosing the digital signature method
Configure the security bindings on a server acting as a client using the console