SOA 11g: B2B Does Not Send ebMS SecurityFailure Error Message Back To The Message Service Handler
(Doc ID 1363920.1)
Last updated on APRIL 23, 2019
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When B2B validates an inbound ebMS message and find something wrong with the signature it log the message "B2B-51924: Message failed the security check"
According to the ebMS 2.0 specification it is strongly RECOMMENDED that "the error is reported to the Message Service Handler (MSH) that sent the message in error", in this case with error code "SecurityFailure"
See chapter 22.214.171.124.2 and 126.96.36.199 of http://www.oasis-open.org/committees/ebxml-msg/documents/ebMS_v2_0.pdf
Is there a reason for B2B not to send this error message?
Is it possible for B2B to send this message?
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