Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Security (WS-Security) > Configure Web Services Security during application assembly > Configure XML digital signature for v5.x web services with an assembly tool


Configure trust anchors using an assembly tool

Use an assembly tool to configure trust anchors (that specify keystores which contain trusted root certificates to validate the signer certificate) or trust stores at the application level.

There is an important distinction between Version 5.x and v6 and later applications. The information in this article supports v5.x applications only that are used with WAS v6.0.x and later. The information does not apply to v6.0.x and later applications.

This document describes how to configure trust anchors or trust stores at the application level. It does not describe how to configure trust anchors at the server or cell level. Trust anchors defined at the application level have a higher precedence over trust anchors defined at the server or cell level. We can configure an application-level trust anchor using an assembly tool or the administrative console. This document describes how to configure the application-level trust anchor using an assembly tool. For more information on creating and configuring trust anchors at the server or cell level, see Configure the server security bindings using an assembly tool or Configure the server security bindings .

A trust anchor specifies keystores that contain trusted root certificates, which validate the signer certificate. These keystores are used by the request receiver (as defined in the ibm-webservices-bnd.xmi file) and the response receiver (as defined in the application-client.xml file when web services are acting as client) to validate the signer certificate of the digital signature. The keystores are critical to the integrity of the digital signature validation. If they are tampered with, the result of the digital signature verification is doubtful and comprised. Therefore, IBM recommends that you secure these keystores. The binding configuration specified for the request receiver in the ibm-webservices-bnd.xmi file must match the binding configuration for the response receiver in the application-client.xml file.

Complete the following steps to configure trust anchors using an assembly tool.


Procedure

  1. Configure an assembly tool to work with a Java EE enterprise application. See the related information on Assembly Tools.

  2. Create a web services-enabled Java EE enterprise application. See Configure the server security bindings using an assembly tool or Configure the server security bindings for an introduction on how to manage Web Services Security binding information on the server.

  3. Configure the client-side response receiver, defined in the ibm-webservicesclient-bnd.xmi bindings extensions file.

    1. Use an assembly tool to import your Java EE application.

    2. Click Window > Open Perspective > Other > J2EE.

    3. Click Application Client projects > application_name > appClientModule > META-INF
    4. Right-click the application-client.xml file, select Open with > Deployment Descriptor Editor, and click the WS Binding tab. The Client Deployment Descriptor is displayed.
    5. Locate the Port qualified name binding section and either select an existing entry or click Add, to add a new port binding. The web services client port binding editor displays for the selected port.
    6. Locate the Trust anchor section and click Add. The Trust anchor window is displayed.

      1. Enter a unique name within the port binding for the Trust anchor name.

        The name is used to reference the trust anchor that is defined.

      2. Enter the keystore password, path, and keystore type.

        The supported keystore types are the Java Cryptography Extension (JCE) and Java Cryptography Extension Keystores (JCEKS) types.

      Click Edit to edit the selected trust anchor.

      Click Remove to remove the selected trust anchor.

      When you start the application, the configuration is validated in the run time while the binding information is loading.

    7. Save the changes.

  4. Configure the server-side request receiver, defined in the ibm-webservices-bnd.xmi bindings extensions file.

    1. Click Window > Open perspective > J2EE .

    2. Select the web services enabled EJB or web module.

    3. In the Package Explorer window, click the META-INF directory for an EJB module or the WEB-INF directory for a web module.
    4. Right-click the webservices.xml file, select Open with > Web services editor, and click the bindings tab. The web services bindings editor is displayed.
    5. Locate the web service description bindings section and either select an existing entry or click Add to add a new web services descriptor.

    6. Click Binding configurations. The web services binding configurations editor is displayed for the selected web services descriptor.
    7. Locate the Trust anchor section and click Add. The Trust anchor dialog box is displayed.

      1. Enter a unique name within the binding for the Trust anchor name.

        This unique name is used to reference the trust anchor defined.

      2. Enter the keystore password, path, and keystore type. The supported keystore types are JCE and JCEKS.

      Click Edit to edit the selected trust anchor.

      Click Remove to remove the selected trust anchor.

      When you start the application, the configuration is validated in the run time while the binding information is loading.

    8. Save the changes.


Results

This procedure defines trust anchors that can be used by the request receiver or the response receiver (if the web services is acting as client) to verify the signer certificate.


Example

The request receiver or the response receiver (if the web service is acting as a client) uses the defined trust anchor to verify the signer certificate. The trust anchor is referenced using the trust anchor name.


What to do next

To complete the signing information configuration process for request receiver, complete the following tasks:

  1. Configure the server for request digital signature verification: Verifying the message parts
  2. Configure the server for request digital signature verification: choosing the verification method

To complete the process for the response receiver, if the web services is acting as a client, complete the following tasks:

  1. Configure the client for response digital signature verification: verifying the message parts
  2. Configure the client for response digital signature verification: choosing the verification method


Trust anchors
Assembly tools
Assembling applications
Configure the server security bindings using an assembly tool
Configure the server security bindings
Configure the server for request digital signature verification: Verifying the message parts
Configure the server for request digital signature verification: choosing the verification method
Configure the client for response digital signature verification: verifying the message parts
Configure the client for response digital signature verification: choosing the verification method
Secure web services for v5.x applications using XML digital signature

+

Search Tips   |   Advanced Search