MFT / Reference / AS/2 Connector

AS/2 Connector

The AS/2 connector allows you to exchange documents using the AS/2 protocol.

Create new AS/2 Connector

You can create a new connector by going to Settings -> Connectors and click on the action “New Connector”. You can give the connector a name and a description. Then choose AS/2 as the connector type.

You can configure the following properties:


This is you AS/2 ID for this connector. You can create multiple connectors. Each connector will have it’s own AS/2 id and certificates to identify your company. You will configure the partner settings later.

To ensure compatibility, we recommend using only letters and numbers for the ID.

Contact E-Mail

This information is used to generate a self-signed certificate for this AS/2 station. You can change the certificate later.

After the connector is created, you can download the public part of the key by clicking “Download Certificate” in the connector’s card. Alternatively you can upload your own private and public key using the action “Upload Private Key”.

You will need to share the following information with your partner:

Endpoint Url

This is the URL where the connector can be reached. We support http (port 80) and https (port 443). We highly recommend to use SSL, so the full URL will start with “https://” and the information shown in the card.


Your self-assigned ID that you’ve choosen when creating the connector.

Public Key / Certificate

The public part of your encryption and signing key. It can be downloaded from the connector. We only support one certificate for encryption and signing on our side.


Message delivery notifications are used to prove that a file has been transfered. We can send synchronous MDNs and no MDNs. And we can receive synchronous and asynchronous MDNs.


The encryption is defined per partner. We do support encryption and signing. Please see in the partner setup the available algorithms. AS/2 can encrypt the data on the transport stream (using https) as well as the data. Using both encryption methods will not necessarily improve the security. We highly recommend to use at least the https encryption, if possible.


We can sign outgoing messages. The setup is defined in each partner.

Content Transfer Coding

We can receive binary and base64 encoded messages. You can at the moment not configure the behavior for sending, so both should be acceptable for your partner.

Create AS/2 Partner

Each AS/2 station can have multiple partners. You can decide whether you want to create a signle station for all your partners or a dedicated connector for each partner.

To create a new partner navigate to the AS/2 connector card page. On the partner subpage click on “New”. You will have to provide the following information:


The name of the partner. This information is just used in the user interface of the portal.


Optional. You can take some notes regarding the connection.

Partner Code (ERP System):

This code has to be unique and is used to identify the partner to the connected ERP system.


The AS/2 id of your partner used to identify him. This has to be unique per connector. In case two of your partner want to use the same ID you have to use a second AS/2 connector.

Endpoint URL

The AS/2 URL of your partner including “https://” or “http://” depending on whether to use SSL encryption or not.

Encryption Certificate

Optional. If the partner sends encrypted messages you’ll have to specify his public key / certificate.

Signing Certificate

Optional. The certificate to validate the signature of your partner. This information is currently not used.

Signature Algorithm

Whether to sign data you’re sending to the partner and which algorithm to be used. This specifies how we’re sending data. You cannot configure whether the partner has to send signed messages at the moment. We do accept signed and unsigned messages.

Encryption Algorithm

Whether we want to send encrypted data and what algorithms to be used. You cannot configure whether the partner has to send encrypted messages at the moment. We do accept incoming encryption and check against the encryption certificate.