OWSM Client Policy For Message Protection Doesn't Support "Strict Layout" (Doc ID 1484127.1)

Last updated on MARCH 30, 2016

Applies to:

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

Symptoms

OWSM policies were used to integrate a service developed with WCF (Microsoft environment) into OSB 11.1.1.5. This service is secured using WS-Security 1.2. The requirements are:

 


  By upgrading the domain to OSB 11.1.1.6, the policy called oracle/wss11_username_token_with_message_protection_client_policy helped to deal with DerivedKeys. Unfortunately, there is no option for the strict layout.
  Indeed, when the policy is applied to an outbound message, two header elements (EncryptedData) are put in a bad order.

Cause

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