B2B 11g - Enforce Signing and Encryption on Incoming AS2 Message

(Doc ID 1901001.1)

Last updated on JULY 10, 2016

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


Use case with Oracle B2B as gateway for interfacing external parties with AS2 protocol for communication.

Need to enforce incoming message to be signed and encrypted.

However, unencrypted messages are being processed without errors.


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