OWSM Client Policy For Message Protection Doesn't Support "Strict Layout"
(Doc ID 1484127.1)
Last updated on FEBRUARY 06, 2019
Applies to:Oracle Web Services Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
OWSM policies were used to integrate a service developed with WCF (Microsoft environment) into OSB 22.214.171.124. This service is secured using WS-Security 1.2. The requirements are:
- SymmetricBinding as a SecurityBinding,
- Derived Keys,
- Strict Layout (recommended option).
By upgrading the domain to OSB 126.96.36.199, 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.
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