Oracle Service Bus 220.127.116.11 MTOM Attachment Policy With OWSM Security Policy Not Working As Expected
(Doc ID 2752434.1)
Last updated on APRIL 04, 2021
Applies to:Oracle Service Bus - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
We are trying to process attachments as binary data through Oracle Service Bus 22.214.171.124 services. We are using MTOOM attachment policy and pass attachment to downstream service as binary data. When we add OWSM security policy that validates the username/password against OID, ctx:binary-content is empty/missing. Instead the content is passed as inline base64 string.
The same scenarios if we try in 126.96.36.199 we are able to receive the binary content in ctx:binary-content reference. There is no official documentation we could find to make sure that if there is any implementation change from 188.8.131.52 to 12.2.14 that made ctx:binary-content with OWSM security and MTOM Policy available in 184.108.40.206 but not in 220.127.116.11.
Could you please confirm if the attachments sent using MTOM Policy with OWSM security is converted to inline base64 string in 18.104.22.168?
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