Configure the server for response signing: choosing the digital signature method

 

Before you begin

Important distinction between V5.x and v6.x applications

Note: The information in this article supports v5.x applications only that are used with WAS v6.x. The information does not apply to v6.0.x applications.

Prior to completing these steps, read either of the following topics to become familiar with the Extensions tab and the Binding configurations tab in the Web services editor within the assembly tools such as the Application Server Toolkit or Rational Web Developer:

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 digital signature method to use when configuring the server for response signing:

 

Procedure

  1. Launch an assembly tool. For more information on the assembly tools, see Assembly tools.

  2. Click Windows > Open perspective > Other > J2EE.

  3. Click EJB Projects > application _name >ejbModule > META-INF

  4. Right-click the webservices.xml file and click Open with > Web services editor.

  5. Click the Binding Configurations tab.

  6. Expand Response sender binding configuration details > Signing information.

  7. Click Edit to choose a signing method. The signing info dialog is displayed and either select or enter the following information:

    • Canonicalization method algorithm

    • Digest method algorithm

    • Signature method algorithm

    • Signing key name

    • Signing key locator

    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 address: 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. Use the same algorithm on the client response receiver. The algorithm selected for the server response sender configuration must match the algorithm selected in the client response receiver configuration.
    Digest method algorithm Applies to the data after transforms are applied, if specified, to yield the <DigestValue> element. Signing the <DigestValue> binds resource content to the signer key. The algorithm selected for the server response sender configuration must match the algorithm selected in the client response receiver configuration.
    Signature method algorithm Converts the canonicalized <SignedInfo> element into the <SignatureValue> element. The algorithm selected for the server response sender configuration must match the algorithm selected in the client response 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 key store where the alias and certificate exists. For more information on configuring key locators, see any of the following files:

 

Result

You have specified which method is used to digitally sign a message when the server sends a message to a client.

 

What to do next

After you configure the server to digitally sign the response message, configure the client to verify the digital signature contained in the response message. See Configuring the client for response digital signature verification: verifying the message parts for more information.


 

See Also


Response sender
Response receiver
XML digital signature

 

Related Tasks


Configuring key locators using an assembly tool
Configuring key locators using the administrative console
Configuring server and cell level key locators using the administrative console
Configuring the server for response signing: digitally signing message parts
Configuring the server security bindings using an assembly tool
Configuring the server security bindings using the administrative console