Securing AS4 messages

AS4 Microservice features ebMS 3.0 AS4 encryption standards for inbound and outbound messaging transactions.

AS4 is a specification of OASIS ebMS 3.0 for conformance policies. AS4 is based on the principles of the AS2 specification. It features such enhancements as compatibility with industry web service standards, message pull capability, and a built-in receipt mechanism. In AS4 Microservice, AS4 also supports the compression, signature, and encryption for inbound and outbound messaging transactions with or without payloads. Both asymmetric and symmetric encryption are implemented for each transaction with public and private keys for added security. Verification and decryption are also supported when you choose a certificate alias.

Note: For Anonymous Partner, you must use the embedded certificate for verification. You cannot configure the verification certificate in the Security Policy page.

When you configure an AS4 conformance policy, you are able to specify multiple options: an encryption algorithm with key strength level, a security reference type, a key transport algorithm, and certificate aliases for encryption and decryption. You can also specify encryption enabled conformance policies for exchange profiles. To use encryption algorithms with an AS4 conformance policy, the Java Cryptography Extension (JCE) policy must be installed with AS4 Microservice. For more information about installing a JCE policy, see Securing Java Cryptography Encryption.