Choosing the digital signature method
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...
- Configuring the client security bindings using the WAS Toolkit
- 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. You must 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 for more information. Complete the following steps to specify which message parts to digitally sign when configuring the client for request signing...
- Launch the Assembly Toolkit and click Windows > Open Perspective > J2EE.
- Select the Web services enabled 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 webservicesclient.xml file and click Open With > Web Services Client Editor.
- Click the Port Binding tab.
- Expand Security Request Sender Binding Configuration > Signing Information.
- Select Edit to view the signing information and select a digital signature method from the Signature method algorithm field. The following table describes the purpose of this information. Some of these definitions are based on the XML-Signature specification, which is located at the following Web site http://www.w3.org/TR/xmldsig-core .
Name Purpose Canonicalization method algorithm Canonicalizes the <SignedInfo> element before the information is digested as part of the signature operation. Digest method algorithm Applies to the data after transforms are applied, if specified, to yield the <DigestValue> element. Signing the <DigestValue> element binds the resource content to the signer key. The algorithm selected for the client request sender configuration must match the algorithm selected in the server request receiver configuration. Signature method algorithm Converts the canonicalized <SignedInfo> element into the <SignatureValue> element. The algorithm selected for the client request sender configuration must match the algorithm selected in the server request receiver configuration. Signing key name Represents the key entry associated with the signing key locator. The key entry refers to an alias of the key, which is found in the key store and is used to sign the request. Signing key locator Represents a reference to a key locator implementation class that locates the correct hey store where the alias and the certificate exist.
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 method is used to digitally sign a message when the client sends a message to a server.
After you configure the client to digitally sign the message, you must configure the server to verify the digital signature. See Configuring the server for request digital signature verification... Verifying the message parts for more information.
See AlsoXML digital signature
Securing Web services using XML digital signature
Configuring the client security bindings using the Assembly Toolkit
Configuring the security bindings on a server acting as a client using the administrative console
Configuring the client for request signing: Digitally signing message parts
Configuring the server for request digital signature verification: verifying the message parts
Configuring key locators using the Assembly Toolkit
Configuring key locators using the administrative console