The Action Field (in Transport Header) Is Null In Callout From OSB To Business Service When Using OWSM X509 Policy
Last updated on DECEMBER 02, 2016
Applies to:Oracle Web Services Manager - Version 220.127.116.11.0 and later
Oracle Service Bus - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The action filed that is set in the content-type of the transport header is going out as null in the call to business service. This works perfectly fine in 11g. We recently upgraded to 12c, and the exact same code/configuration that works in 11g does not work in 12c.
The Service is a SOAP 1.2 service that expects the SOAP action to be set in the content-type transport header, and not the SOAP header as would be the case in SOAP 1.1.
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