AS2 Listener
AS2 Listener
AS2 stands for Applicability Statement 2.
AS2 (Applicability Statement 2) is a specification about how to transport structured business-to-business data securely and reliably over the internet. Security is achieved by using digital certificates and encryption.
The AS2 listener is used to receive AS2 messages over HTTP or HTTPS, package them into ConnectMessages, and send them down the flow.
The listener supports various decryption and signature verification schemes. AS2 trading partners can thus exchange data with the AS2 listener ensuring both confidentiality, authenticity, and data integrity. The certificates required for these operations are stored in the ConnectPlaza key- and trust store which can be managed in the Deploy tab of the ConnectPlaza frontend.
The AS2 listener handles conversion of AS2 messages to ConnectMessages. The listener can output three types of ConnectMessageParts, i.e. text, XML and binary, corresponding to the types of business data contained in an AS2 message. Furthermore, the listener can copy headers from the AS2 message to the ConnectMessagePart.
Finally, in the case of non-compliant AS2 senders, the AS2 listener offers various compatibility options, e.g. it can force message decryption even though its message headers claim it is not encrypted.
In the table below, you will find an explanation of these properties. All attributes with a ‘*’ are mandatory.
Attribute |
Description |
Name* |
By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional. |
Enabled |
Set this value to true if you want this consumer to be enabled. |
MessagePart* |
Name of the MessagePart in a ConnectMessage where the received AS2 message's payload is stored. |
Hostname | The host name of the AS2 consumer. If left empty, it defaults to the standard Jetty (SSL) host name. |
Port | The port number used by the AS2 consumer. If left empty it default to the standard Jetty (SSL) port. |
Context Path | The path appended to host:port. Note that this must start with a forward slash ('/'). |
Sender ID* | The AS2 ID of the partner sending to the AS2 consumer. |
Sender X509 Alias | The alias used to retrieve the sending partner's public key from the KeyStore. |
Receiver ID* | The AS2 ID of the AS2 consumer. |
Receiver Key Pair Alias | The alias used to retrieve the AS2 consumer's private and public key from the KeyStore. |
MessagePart Content Type | Content type of the outgoing ConnectMessagePart. |
Charset |
Condition: MessagePart Content Type = TEXT The canonical name of the Java charset set to decode the AS2 message payload. If left empty, it defaults to the system default. Besides the values in the drop down, you can also use other charset values. Consult your Java documentation for supported encodings. |
Mapped Request Headers | A comma separated list of headers to be mapped from an AS2 message to the ConnectMessage. |
Enable TLS/SSL | Enable TLS/SSL support. |
TLS Certificate Alias |
Condition: Enable TLS/SSL = true AS2 consumer's certificate alias for TLS/SSL purposes. |
Verify Using Certificate In Body | Define whether a certificate passed in the signed MIME body part shall be used to verify the signature or whether to use the certificate in the trust store. |
Disable Decryption | Set whether to disable decryption of the received message, even if the Content-Type header claims the message is encrypted. This is a work-around for non spec-compliant senders. |
Force Decryption | Set whether to force decryption of a received message, even if the Content-Type header claims the message is not encrypted. This is a work-around for non spec-compliant senders. |
Disable Signature Verification | Set whether to disable signature verification of a received messages, even if the Content-Type header claims the message is signed. This is a work-around for non-spec-compliant senders. |
Force Signature Verification | Set whether to force signature verification of a received message, even if the Content-Type header claims the message is not signed. This is a work-around for non-spec-compliant senders. |
Disable Decompression | Set whether to disable decompression of a received message, even if the Content-Type header claims the message is compressed. This is a work-around for non spec-compliant senders. |
Description |
Description of the specific consumer. This is for documentation purposes. |