Search

Home

Home

gravity.integration
gravity.integration
/gravity.integration ENG
gravity.integration ENG
/Technical Documentation
Technical Documentation
/GRAVITY.INTEGRATION Environment
GRAVITY.INTEGRATION Environment
/System Configuration
System Configuration
/Connections to sources/destinations
Connections to sources/destinations
/
New AS2 Connection

New AS2 Connection

icon

Within the AS2 protocol, each business partner must be defined in the system to ensure secure and correct document exchange. An AS2 partner is a remote system that sends or receives messages using predefined identifiers, certificates, cryptographic algorithms, and an HTTP(S) endpoint.

To create a new AS2 partner connection, select AS2 Partners and use the New… button.

image

To add a new AS2 partner, complete the following configuration fields:

image
  • Name - Partner name, used internally in the application (e.g., PartnerX).
  • AS2Id - Unique identifier of the partner in the AS2 protocol (the AS2-From header). It has to exactly match the value agreed upon with the partner.
  • Partner certificate path - Path to the partner’s public certificate file (e.g., .cer, .crt, .pem). Used to verify the digital signature and encrypt outgoing messages.
  • Signature algorithm - Digital signature algorithm used for signing messages.
    • None – no signature
    • MD5
    • SHA1
    • SHA256 (recommended)
    • SHA512
  • Encryption algorithm - Encryption algorithm used for messages sent to the partner. It has to be supported by the partner; strong algorithms (e.g., AES256) are recommended.
    • No encryption
    • AES128
    • AES192
    • AES256 (recommended)
    • 3DES
  • Payload content type - The content type of transmitted documents. It has to match the data format agreed upon with the partner.
    • application/EDIFACT
    • application/edi-x12
    • application/JSON
    • application/XML
  • MDN Type - Type of delivery receipt (MDN – Message Disposition Notification).
    • sync – confirmation sent immediately in the HTTP response
  • Signature MDN - Indicates whether the MDN confirmation should be digitally signed.
  • Server auth type - Type of server (client) authentication used when connecting to the partner.
    • Basic auth – requires providing a username and password
      • icon

      Authentication must comply with the partner’s requirements. In the case of Basic auth, you must also provide fields for the username and password.

icon

Before starting production data exchange, it is recommended to test certificates, signatures, and MDN in a test environment. All cryptographic values (algorithms, certificates) must be agreed upon with the partner in advance.