Before you begin
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 the Assembly Toolkit. These two tabs are used to configure the Web services security extensions and the Web services security bindings, respectively.Why and when to perform this task
Complete the following steps to specify which message parts to digitally sign when configuring the client for request signing:Steps for this task
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.
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
Note: 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 the Assembly Toolkit:
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:
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.
After you specify which message parts to digitally sign when the client sends a message to a server.What to do next
Once you have specified which message parts to digitally sign, you must specify which method is used to digitally sign the message. See Configuring the client for request signing: Choosing the digital signature method for more information.