+

Search Tips   |   Advanced Search

Set the signing information using JAX-RPC for the generator binding on the application level


Configure the signing information for the client-side request generator and the server-side response generator bindings at the application level.

For transitioning users: For WAS version 6.x or earlier only, in the server-side extensions file (ibm-webservices-ext.xmi) and the client-side deployment descriptor extensions file (ibm-webservicesclient-ext.xmi), specify which parts of the message are signed. Also, configure the key information that is referenced by the key information references on the signing information panel within the admin console.trns

This task explains the required steps to configure the signing information for the client-side request generator and the server-side response generator bindings at the application level. WAS uses the signing information for the default generator to sign parts of the message including the body, time stamp, and user name token. The Application Server provides default values for bindings. However, an administrator must modify the defaults for a production environment. Complete the following steps to configure the signing information for the generator sections of the bindings files on the application level:

 

  1. Locate the signing information configuration panel in the admin console.

    1. Click Applications > Application Types > WebSphere enterprise applications > application_name.

    2. Under Manage modules, click URI_name.

    3. Under WS-Security Properties, we can access the signing information for the request generator and the response generator bindings.

    4. Under Required properties, click Signing information.

    5. Click New to create a signing information configuration, select the box next to the configuration and click Delete to delete an existing configuration, or click the name of an existing signing information configuration to edit its settings. If creating a new configuration, enter a name in the Signing information name field. For example, we might specify gen_signinfo.

  2. Select a signature method algorithm from the Signature method field.

    The algorithm specified for the generator, which is either the request generator or the response generator configuration, must match the algorithm specified for the consumer, which is either the request consumer or response consumer configuration. WAS supports the following pre-configured algorithms:

  3. Select a canonicalization method from the Canonicalization method field.

    The canonicalization algorithm specified for the generator must match the algorithm for the consumer. WAS supports the following pre-configured algorithms:

    • http://www.w3.org/2001/10/xml-exc-c14n#

    • http://www.w3.org/2001/10/xml-exc-c14n#WithComments

    • http://www.w3.org/TR/2001/REC-xml-c14n-20010315

    • http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments

  4. Select a key information signature type from the Key information signature type field. WAS supports the following signature types:

    None

    The <KeyInfo> element is not signed.

    Keyinfo

    The entire <KeyInfo> element is signed.

    Keyinfochildelements

    The child elements of the <KeyInfo> element are signed.
    The key information signature type for the generator must match the signature type for the consumer. We might encounter the following situations:

    • If we do not specify one of the previous signature types, WAS uses keyinfo, by default.

    • If we select Keyinfo or Keyinfochildelements and you select http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform as the transform algorithm in a subsequent step, WAS also signs the referenced token.

  5. Select a signing key information reference from the Signing key information field. This selection is a reference to the signing key that the appserver uses to generate digital signatures.

  6. Click OK and Save to save the configuration.

  7. Click the name of the new signing information configuration.

    This configuration is the one specified in a previous step.

  8. Specify the part reference, digest algorithm, and transform algorithm.

    The part reference specifies which parts of the message to digitally sign.

    1. Under Additional properties, click Part references > New to create a new part reference, click Part references > Delete to delete an existing part reference, or click a part name to edit an existing part reference.

    2. Specify a unique part name for this part reference. For example, we might specify reqint.

    3. Select a part reference from the Part reference field.

      The part reference refers to the message part that is digitally signed. The part attribute refers to the name of the <Integrity> element in the deployment descriptor when the <PartReference> element is specified for the signature. We can specify multiple <PartReference> elements within the <SigningInfo> element. The <PartReference> element has two child elements when it is specified for the signature: <DigestTransform> and <Transform>.

    4. Select a digest method algorithm from the menu. The digest method algorithm specified within the <DigestMethod> element is used in the <SigningInfo> element. WAS supports the following algorithms:

      • http://www.w3.org/2000/09/xmldsig#sha1

      • http://www.w3.org/2001/04/xmlenc#sha256

      • http://www.w3.org/2001/04/xmlenc#sha512

    5. Click OK to save the configuration.

    6. Click the name of the new part reference configuration.

      This configuration is the one specified in a previous step.

    7. Under Additional Properties, click Transforms > New to create a new transform, click Transforms > Delete to delete a transform, or click a transform name to edit an existing transform. If we create a new transform configuration, specify a unique name. For example, we might specify reqint_body_transform1.

    8. Select a transform algorithm from the menu. The transform algorithm is specified within the <Transform> element and specifies the transform algorithm for the signature. WAS supports the following algorithms:

      • http://www.w3.org/2001/10/xml-exc-c14n#

      • http://www.w3.org/TR/1999/REC-xpath-19991116 Restriction: Do not use this transform algorithm if we want the configured application to be compliant with the Basic Security Profile (BSP). Instead use http://www.w3.org/2002/06/xmldsig-filter2 to ensure compliance.

      • http://www.w3.org/2002/06/xmldsig-filter2

      • http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform

      • http://www.w3.org/2002/07/decrypt#XML

      • http://www.w3.org/2000/09/xmldsig#enveloped-signature

      The transform algorithm that you select for the generator must match the transform algorithm that you select for the consumer.

      If both of the following conditions are true, WAS signs the referenced token:

      • You previously selected the Keyinfo or the Keyinfochildelements option from the Key information signature type field on the signing information panel.

      • You select http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform as the transform algorithm.

  9. Click Apply.

  10. Click Save at the top of the panel to save the configuration.

 

Results

After completing these steps, the signing information is configured for the generator on the application level.

 

Next steps

Specify a similar signing information configuration for the consumer.


Signing information collection
Signing information settings
Part reference collection
Part reference settings
Transforms collection
Transforms settings

 

Related concepts


Basic Security Profile compliance tips

 

Related tasks


Set the signing information using JAX-RPC for the consumer binding on the application level
Set generator signing using JAX-RPC to protect message integrity