AS2 Connector Release Notes - Mule 4

You can now configure the Send with Sync Mdn operation to use a different certificate for MDN signature validation than the one used for encryption.

You can now configure the As2 listener source so that it rejects new, incoming messages that have the same sender, receiver, and message ID as messages that have been processed already.

You can now configure the As 2 listener source to send the MDN at the end of the flow by using the Mdn mode option AUTO.

You can now configure retries to ensure the delivery of the MDN by using the Retry interval and Retry count fields in the Async MDN Connection Provider global configuration.

A new field named Validate certificate expiration date enables you to enable or disable the certificate expiration date validation.

The console logs a warning message when a certificate approaches its expiration date or if it already expired. You can configure when to get the warning by using the new Warning before (days) in the KeyStore Config field.

The bcprov-jdk15on is upgraded to version 1.69.

The bcpkix-jdk15on library is upgraded to version 1.69.

You can now configure a single AS2 listener endpoint to receive messages from multiple partners by using the Shared listener mode option.

You can now pass custom headers on outbound AS2 messages when using the Send with Sync MDN and Send with Async MDN operations.

The new Custom Message ID property enables you to specify a custom message ID for AS2 send operations.

The new Propagate Content Transfer Encoding property indicates whether to propagate the content transfer encoding on the AS2 message sent to the partner.

Added a new configuration to optionally enable or disable chunked data transfer in the Send operation.

Changed the reporting-UA parameter to an optional parameter in the MDN listener.

AS2 Listener did not clear incoming payloads, which caused the /tmp directory to become full and a 'java.io.IOException: No space left on device' error. (SE-17914)

The issue that caused a memory leak with Bouncy Castle javax.crypto.JceSecurity in applications with an AS2 Receiver is fixed. (SE-17950)

The Subject parameter was not being applied to outgoing AS2 messages.

Non-repudiation of a signed message is now implemented for all operations and sources in AS2 Connector.

AS2 Send with Sync MDN operation now outputs the MDN payload to the user flow instead of the original payload.

AS2 Send with Async MDN operation now outputs nothing (void) to the user flow instead of the original payload.

AS2 Connector IO performance is improved on CloudHub, as the Send operations no longer retain the original payload.

Mule 4.3.0 enables a more efficient way of dispatching reusable streams to the Mule flow by using ImmutableRepeatableFileInputStream.

Added support for dynamically passing a Partner URL in AS2 Send operations.

The securityLevel configuration parameter sets the Security level requirement on the AS2 Listener to accept only signed, encrypted, or signed-and-encrypted based on your organization’s security guidelines.

The issue that caused a memory leak with Bouncy Castle javax.crypto.JceSecurity in applications with an AS2 Receiver is fixed. (CONN-7171)

Fixed security vulnerability issues (CONN-6397).

Signed copies of the document for non-repudiation are not saved.

Validation of the as2-to and as2-from headers did not produce the expected error response (CONN-5653).

Signed copies of the document for non-repudiation are not saved.

Basic Authentication is now available for both send operations and on a receiving source.

Support using the MIME type set on the input message for AS2 send data (CONN-4668)(SE-13003).

Signed copies of the document for non-repudiation are not saved.

Fixed the issue where an MDN was not requested or sent, which resulted in an NPE with the payload not being passed to the Mule flow. (SE-14740)

Signed copies of the document for non-repudiation are not saved.

Authentication over HTTP is currently not supported.

All operations support message payloads as a stream.

Experience using Anypoint Studio to configure Mule 4 application flows using HTTP endpoint configuration is improved, and new error types that improve error handling are available.

An explicit asynchronous MDN source enables you to process asynchronous MDN in the application.

CloudHub configuration is improved.

Information from the AS2 Send and Listener operation output attributes is more detailed.

Additional encryption/signing algorithms are now supported.

Signed copies of the document for non-repudiation are not saved.

Authentication over HTTP is currently not supported.

Fixed startup error due to a slash (/) in the windows path. (SE-14173)

The java.nio.file.Files.copy() file is now used instead of the Apache Commons IO library for a file copy, fixing the "Error storing transaction" error caused by "java.io.IOException: Failed to copy full contents". (SE-14144)

The mime type is now a configurable value in the partnership configuration for outgoing messages. This enables users to set the content type of the sending document. (SE-13317)

Resolved a directory polling issue if the config folder is missing during runtime(SE-11935).

Corrected NullPointerException thrown during HTTP response generation for error conditions (SE-11935).

The AS2 Connector did not refer an SSL certificate from the keyStorePath specified in the Secure Receiver Module ports.

Certain receive requests failed because the App was trying to process deleted files.

Some send and receive requests failed because the app was starting to process files before they were completely transferred.

Releasing threads and file operations from the Send process increased the size of the thread pool and caused many operations to fail.

The send and receive operations were not supported together in the same instance.

The connector always sent the content signed with SHA256.

The connector did not accept JKS and JCEKS keystores.

The encryption and signing algorithm lists in the configuration are now tho separate ones. Previously, you were able to select a signing algorithm for encrypting and vice-versa, which would not work.

The connector is now able to receive both signed and unsigned MDNs.

Added Receiver Host configuration, which must be set to "0.0.0.0" for operating on CloudHub.

The connector would not accept incoming messages when run on CloudHub.

Using signing throws ClassCastException.

Send - Allows you to send AS2 messages via HTTP or HTTPS.

Receive - Enables a Mule application to receive messages following the AS2 protocol.

MuleSoft Help Center