Digital signature verification failure in DataPower SOA appliance.

Cause:
The hash DataPower generated of the reference node(s) did not match the hash provided by the original signer in the DigestValue node. Typically this is caused by one of the following:

• The processing policy modified the data
• The message was modified by a intermediate node
• Improper handling by the signing application

Error:

Cause:
The most common causes are as follows:

• The device has an HSM that has not been initialized. RSA operations are not available on HSM enabled devices until the unit is initialized.  For details on the initialization process, see Intializing the HSM
• The private key used to sign the request does not match the specified certificate. If both keys are already stored on DataPower, you can confirm that the keys match using an IDCred. If it is up after adding both keys, they match, otherwise they may not.
• The SignedInfo nodeset was modified after the signature was generated. This may occur for the same reasons as the hash/digest mismatch.
• The SignatureValue itself was modified.
• The signature verification is performed using a custom style sheet that is not implemented properly.