Before you begin
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. For more information on creating and configuring trust anchors at the server or cell level, see either Configuring the server security bindings using an assembly tool or Configuring the server security bindings using the administrative console.
You 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 the administrative console.
Why and when to perform this task
A trust anchor specifies key stores that contain trusted root certificates, which validate the signer certificate. These key stores are used by the request receiver (as defined in the ibm-webservices-bnd.xmi file) and the response receiver (as defined in the ibm-webservicesclient-bnd.xmi file when Web services is 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, it is recommended 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 ibm-webservicesclient-bnd.xmi file.
The following steps are for the client-side response receiver, which is defined in the ibm-webservicesclient-bnd.xmi file and the server-side request receiver, which is defined in the ibm-webservices-bnd.xmi file.
Steps for this task
When you start the application, the configuration is validated in the run time while the binding information is loading.
Enter a unique name within the request receiver binding for the Trust anchor name field. The name is used to reference the trust anchor that is defined.
Enter the key store password, path, and key store type.
Click the trust anchor name link to edit the selected trust anchor.
Click Remove to remove the selected trust anchor or anchors.
When you start the application, the configuration is validated in the run time while the binding information is loading.
Result
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
What to do next
To complete the signing information configuration process for request receiver, complete the following tasks: To complete the process for the response receiver, if the Web services is acting as client, complete the following tasks:Related concepts
Trust anchors
Related tasks
Configuring the server security bindings using an assembly tool
Configuring the server security bindings using the administrative console
Developing Web services applications
Configuring the server for request digital signature verification:
Verifying the message parts
Configuring the server for request digital signature verification:
choosing the verification method
Configuring the client for response digital signature verification:
verifying the message parts
Configuring the client for response digital signature verification:
choosing the verification method
Securing Web services for version 5.x applications using XML digital
signature