AS2

<< Click to Display Table of Contents >>

Navigation:  Reference > Settings >

AS2

Ref_AS2_006

 

AS2 message settings

 

Own AS2 identifier

Your own AS2 identifier. The AS2 identifier can be freely selected, but should be as unique as possible. For example, a DUNS number, Odette identifier or an e-mail address can be used here.

 

Message IDs

The format for the IDs of outgoing messages. Each AS2 message should have a unique ID. For the left part of the ID currently only the Timestamp option can be selected. The Timestamp contains the current date at the time of sending and the time including milliseconds. The right part of the ID is freely selectable. Usually the host name under which the AS2 installation can be reached is used here, for example edi.bartschsoft.de.

 

Asynchronous MDN URL

The URL to which the far end should send asynchronously requested acknowledgements (MDNs). Used only when confirmations are requested or sent asynchronously by a partner. If MDNs are only received synchronously, this field can remain empty.

 

Debugging

 

AS2 debugging can be enabled here. If debugging is enabled, detailed information about incoming and outgoing connections is logged in log directory in the file DebugAS2.txt. Debugging should only be enabled for error analysis in case of problems.

 

Server settings

 

Enable AS2 server

Activates or deactivates the integrated AS2 server. The AS2 server must be activated for incoming connections.

 

Port

The port on which to respond to incoming connections.

 

Security level

The security level determines which ciphersuites are supported for incoming TLS connections. The options available are High, Standard, Compatible and Insecure.

 

High offers the best security.

Standard offers a good balance between adequate security and compatibility.

Compatible also allows older clients to connect to !MC5, with medium restrictions regarding the security of the ciphersuites used.

Insecure should only be used if partners with outdated AS2 software would otherwise not be able to connect to !MC5.

 

You can view the exact list of activated ciphersuites by clicking on the Show security details button.

 

Client authentication

If this option is enabled, !MC5 requests the certificate of the client for an incoming TLS connection. Only if the client sends a certificate and it can be found in the partner database of !MC5, the connection is established. You can use this function to make sure that already on TLS level only partners known to you can establish a connection.

 

TLS versions

Here you can select which TLS versions should be supported for incoming connections. TLS 1.0 is considered insecure and should only be activated if a partner uses outdated software that does not support a higher version. The fewer "old" TLS versions are enabled, the more secure. The settings apply to all incoming AS2 connections.

 

Certificates

 

To allow incoming AS2 connections, at least one certificate for TLS authentication must be stored here. Depending on the AS2 functions used (encryption, signing of messages or confirmations), certificates for other purposes must be specified. One certificate can be used for all purposes, or multiple certificates for different purposes. !MC5 automatically uses the latest valid certificate for the respective purpose. Currently used certificates are displayed in bold.