Audience: All suppliers and retailers currently integrated with the Rithum platform via an AS2 connection.

On February 28, 2022 at 12 PM ET, the platform will be updating its AS2 certificate.

Important: The platform requires that each file sent via AS2 have a unique filename. If a file is transferred and has the same filename as a previous file, it will not be processed.

The platform supports exchanging files via an AS2 server. This article details the technical requirements for connecting via an AS2 server.

The platform supports the AS2 transport protocol using its own AS2 server. The Rithum AS2 server must be configured to communicate with the partner's AS2 server. Likewise, the partner's AS2 server must be configured to communicate with the Rithum AS2 server.

To set up any AS2 connections, please email the Software Support team with your account email address and the information requested below.

AS2 Server Configuration (Single Connection)

Partners need to create a connection in their own AS2 server with the following AS2 configuration information:

  • AS2 ID
    • DscoExAs2
  • AS2 Receipt URL
  • IP Addresses Your Firewall Must Accept
  • Data Encryption
    • 3DES
  • Digital Signature
    • SHA-2
  • Compression
    • NO
  • Request Sync MDN
    • NO
  • Request Signed MDN
    • NO

Certificates

Please send an email to the Software Support team to request the Rithum AS2 certificate. Include the partner's AS2 certificate in your email. Software Support will respond with the Rithum AS2 certificate and server information.

Partner AS2 Server Configuration

Partners need to email the Software Support team with the following settings describing the partner's AS2 configuration. In addition, partners should include their AS2 certificate and any special instructions around a self-signed certificate.

  • AS2 ID
    • <Please provide the partner AS2 ID>
    • Each AS2 server is uniquely identified by a string of characters called the AS2 System Identifier (often referred to as the AS2 ID). The AS2 ID is a string of 1 to 128 ASCII characters and is case-sensitive. The AS2 ID identifies the sender and receiver in AS2 communication and determines which certificates will be used. There is no standard registrar of AS2 IDs and, therefore, no guarantee that each ID will be unique.
  • AS2 Receipt URL
    • <Please provide the partner AS2 Receipt URL>
    • This is the URL which is used by external AS2 servers to communicate with the partner.
  • Data Encryption
    • <Please provide partner Data encryption, one of these values... 3DES, No Encryption, DES, RC2-40, RC2-64, RC2-128, RC2-196, RC4-40, RC4-56, RC4-128, AES-128, AES-192, AES-256>
    • This is the algorithm the partner's AS2 server uses to encrypt the data.
  • Digital Signature
    • <Please provide partner Digital signature, one of these values... No Signature, MD5, SHA-224, SHA-256, SHA-384, SHA-512>
    • This is the algorithm the partner's AS2 server uses to sign the data.
  • Compression
    • <Please specify YES or NO>
    • Whether or not the partner's AS2 server requests compression of the data.
  • Request Sync MDN
    • <Please specify YES or NO>
    • Whether or not the partner's AS2 server requests synchronous MDN.
  • Request Signed MDN
    • <Please specify YES or NO>
    • Whether or not the partner's AS2 server requests MDN responses be signed.

AS2 Server Configuration (Shared Connection)

If you would like to add a new platform account to an existing AS2 connection with your third party, email the Software Support team with the following information:

  • AS2 ID
  • A Unique EDI Sender ID
  • Rithum account email address

Please note that all accounts connected to an existing (shared) connection must be assigned unique EDI ID to ensure that transmitted data is routed to the correct Rithum account.

Was this article helpful?
3 out of 7 found this helpful

Comments

0 comments

Please sign in to leave a comment.