The AS2 Listener source now supports AS2-to and AS2-from header values that have double quotes, in accordance with RFC-4130.
AS2 Connector Release Notes - Mule 4
Support Category: Premium
Anypoint Connector for AS2 (Applicability Statement 2) is a specification about how to transport data securely and reliably over the internet. Security is achieved by using digital certificates and encryption.
Mule runtime engine (Mule) supports the AS2 protocol through the Anypoint Connector for AS2 (AS2 Connector). AS2 Connector enables trading partners to transmit and receive AS2 messages with EDI-X12, EDIFACT, XML, or binary payloads.
6.6.0
June 22, 2023
What’s New
-
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.
To use this feature, select Use different Alias for MDN Signature Validation and complete the x509 Alias For MDN Signature field.
For more information, see the Send Config section in the AS2 Connector Reference.
6.5.0
March 14, 2023
What’s New
-
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.
To use this feature, select the Check for duplicate messages field and reference a global object store in the Object Store field.
For more information, see the AS2 Connector Reference.
6.4.1
December 7, 2022
Fixed Issues
Issue Resolution | ID |
---|---|
The send operations no longer generate a thread leak in the Threshold or Identity transfer modes when the connector is configured with static expression values. |
W-11723371 |
The send operations no longer generate a thread leak in dynamic configuration situations. |
W-11796931 |
Payloads can now be encrypted with the |
W-11888057 |
6.4.0
November 14, 2022
What’s New
-
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.
For more information, see the AS2 Connector Reference.
Fixed Issues
Issue Resolution | ID |
---|---|
The As 2 listener now sends back the MDN if there are errors. |
W-11303187 |
The As 2 mdn listener won’t throw an exception when receiving an MDN without the |
W-11633079 |
When an error occurs in the As 2 listener, the execution of the flow now stops. |
W-11633272 |
If an error occurs when setting the Request a Receipt field to |
W-11633356 |
The connector now cleans the temporal files created when the resource threshold is reached. |
W-11715911 |
The As 2 listener now sends back the HTTP response when an async and unsigned MDN is requested. |
W-11837866 |
6.3.2
6.3.0
June 06, 2022
What’s New
-
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.
Fixed Issues
Issue | ID |
---|---|
Log entry levels no longer print informational log messages. |
W-11099643 |
The performance of the MDN listener under a high load is now improved. |
W-11142320 |
AS2 Send operations now correctly handle an |
W-10580735 |
6.2.3
November 17, 2021
Fixed Issues
Issue | ID |
---|---|
Outbound encrypted messages contained extra |
CONN-9285 |
The connector did not accept the |
SE-23387 |
6.2.0
6.0.2
October 15, 2020
Fixed Issues
-
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)
6.0.0
July 16, 2020
New Features
-
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.
5.1.0
5.0.1
5.0.0
December 2019
New Features
-
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.
4.0.4
May 16, 2019
Fixed Issues
-
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.
4.0.2
March 28, 2019
Fixed Issues
-
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.