Configure the server for request digital signature verification... verifying the message partsPrior to completing these steps, read either of the following topics to become familiar with the Security Extensions tab and the Binding Configurations tab in the Web services editor within the WAS Toolkit...
- Configuring the server security bindings using the WAS Toolkit
- Configuring the server security bindings using the administrative console
Use these two tabs to configure the Web services security extensions and the Web services security bindings, respectively. Also, specify which parts of the message sent by the client must be digitally signed. See Configuring the client for request signing: Digitally signing message parts to determine which message parts are digitally signed. The message parts specified for the client request sender must match the message parts specified for the server request receiver. Complete the following steps to configure the server for request digital signature verification. The steps describe how to modify the extensions to indicate which parts of the request to verify.
- Launch the WAS Toolkit and either click Windows > Open Prospective > Java or Windows > Open Prospective > Resource.
- Select the Web services-enabled Enterprise JavaBean (EJB) or Web module.
- In the Package Explorer window, locate the META-INF directory for an EJB module or the WEB-INF directory for a Web module.
- Right-click the webservices.xml file, and click Open With > Web Services Editor.
- Click the Security Extensions tab in the Web services editor.
- Expand the Request Receiver Service Configuration Details > Required Integrity section.Required integrity refers to the parts of the message that require digital signature verification. The purpose of digital signature verification is to make sure that the message parts have not been modified while transmitting across the Internet.
- Indicate parts of the message to verify by clicking Add, and selecting one of the following three parts: body, timestamp, or SecurityToken. You can determine which parts of the message to verify by looking at the Web service request sender configuration in the client application. To view the Web service request sender configuration information in the Web services client editor, click the Security Extensions tab and expand Request Sender Configuration > Integrity. The following includes a list and description of the message parts...
Body This is the user data portion of the message.
Timestamp The timestamp determines if the message is valid based on the time that the message is sent and then received. If timestamp option is selected, proceed to the next step to Add Created Time Stamp to the message.
Securitytoken The security token authenticates the client. If the SecurityToken is selected, the message is signed.
- (Optional) Expand the Add Received Time Stamp section. The Add Received Time Stamp value indicates to validate the Add Created Time Stamp option configured by the client. You must select this option if you selected the Add Created Time Stamp on the client. The time stamp ensures message integrity by indicating the timeliness of the request. This option helps defend against replay attacks.
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 WAS Toolkit:
- 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 WAS 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.You have specified which message parts are digitally signed and must be verified by the server when the client sends a message to a server.
After you specify which message parts contain a digital signature that must be verified by the server, configure the server to recognize the digital signature method used to digitally sign the message. See Configuring the server for request digital signature verification: Choosing the verification method for more information.
See AlsoSecurity token
Securing Web services using XML digital signature
Configuring the server security bindings using the Assembly Toolkit
Configuring the server security bindings using the administrative console
Configuring the client for request signing: Digitally signing message parts
Configuring the client for request signing: Choosing the digital signature method
Configuring the server for request digital signature verification: choosing the verification method