Why is the EncryptedKey Necessary in the oracle/wss11_x509_token_with_message_protection_service_policy? (Doc ID 1478750.1)

Last updated on MARCH 18, 2016

Applies to:

Oracle Web Services Manager - Version 11.1.1.1 to 11.1.1.6.0 [Release 11gR1]
Information in this document applies to any platform.

Goal

The OWSM Web Service security policy "oracle/wss11_x509_token_with_message_protection_service_policy" requires that an EncryptedKey element be added to the web service request even if no encryption is desired on the request (only a signature). The specifications for wss11 says that this type of policy can be configured to do both signature and/or encryption of portions of the message, so why is the EncryptedKey required?

As well, it has been determined that with the WSS11 policy, if it is set up to sign the Timestamp, the body, and a couple of other parts of the message, the policy seems to be using both hmac-sha1 and rsa-sha1 algorithms for the SignatureMethod.  It seems to be using the hmac-rsa algorithm to sign the Timestamp, while using rsa-sha1 for the rest of the message. Why are two different Signature Methods being used?.

None of this behavior occurs with the WSS10 policy version of the policy.

Why is the wss11 policy not operating as expected?
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms