My Oracle Support Banner

weblogic.xml.crypto.wss.WSSecurityException: Signature failed to validate (Doc ID 2908348.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Oracle Web Services Manager - Version and later
Information in this document applies to any platform.


After following this interoperability document, a signature validation issue occurred. The interoperability issue is between the SOA client and the web service deployed to Weblogic 14.1.1.

In the SOA client, two OWSM policies are attached to the BPEL client:

- oracle/wss11_saml20_token_with_message_protection_client_policy
- oracle/log_policy.

However, on the Weblogic 14.1.1 web service side, the following policies are attached:

- Wssp1.2-2007-Saml2.0-SenderVouches-Wss1.1.xml
- Wssp1.2-2007-SignBody.xml
- Wssp1.2-EncryptBody.xml.

The issue is that one element, the EncryptedKey, has a DigestValue that does not match the unmarshalledDigestValue as it should.  All other elements in the security header do match.

When the web service (in WLS 14.1.1) is called from the client composite (SOA, because of this mismatch, the following error is seen:  


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.