Before you begin
Why and when to perform this task
Complete the following steps to configure the server for request digital signature verification. The steps describe how to modify the extensions to indicate which digital signature method the server will use during verification.Steps for this task
Name | Purpose |
---|---|
Canonicalization method algorithm | Canonicalizes the <SignedInfo> element before it is digested as part of the signature operation. The algorithm selected for the server request receiver configuration must match the algorithm selected in the client request sender configuration. |
Digest method algorithm | Applies to the data after transforms are applied, if specified, to yield the <DigestValue> element. The signing of the <DigestValue> element binds resource content to the signer key. The algorithm selected for the server request receiver configuration must match the algorithm selected in the client request sender configuration. |
Signature method algorithm | Converts the canonicalized <SignedInfo> element into the <SignatureValue> element. The algorithm selected for the server request receiver configuration must match the algorithm selected in the client request sender configuration. |
Use certificate path reference or Trust any certificate | Validates a certificate or signature sent with a message. When a message is signed, the public key used to sign it is sent with the message. This public key or certificate might not be validated at the receiving end. By selecting User certificate path reference, you must configure a trust anchor reference and a certificate store reference to validate the certificate sent with the message. By selecting Trust any certificate, the signature is validated by the certificate sent with the message without the certificate itself being validated. |
Use certificate path reference: Trust anchor reference | Refers to a key store that contains trusted, self-signed certificates and certificate authority (CA) certificates. These certificates are trusted certificates that you can use with any applications in your deployment. |
Use certificate path reference: Certificate store reference | Contains a collection of X.509 certificates. These certificates are not trusted for all applications in your deployment, but might be used as an intermediary to validate certificates for an application. See |
Result
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.
What to do next
After you configure the client for request signing and the server for request digital signature verification, you must configure the server and the client to handle the response. Next, specify the response signing for the server. See Configuring the server for response signing: digitally signing message parts for more information.Related concepts
XML digital signature
Request sender
Request receiver
Related tasks
Configuring the server security bindings using an assembly tool
Configuring the server security bindings using the administrative console
Configuring the server for request digital signature verification:
Verifying the message parts
Configuring trust anchors using an assembly tool
Configuring trust anchors using the administrative console
Configuring the server-side collection certificate store using an assembly
tool
Configuring the client-side collection certificate store using an assembly
tool
Configuring the client-side collection certificate store using the
administrative console
Configuring default collection certificate stores at the server level
in the WebSphere Application Server administrative console
Configuring the server for response signing: digitally signing message
parts
Related information
XML-Signature Syntax and Processing: W3C Recommendation 12 February
2002