Note: It’s important that you do not make any changes to your connection until we reach out to you in early 2025 with your migration date and next steps. No action is required at this time.

As part of Rithum's commitment to ensure the highest level of data security, we are in the process of upgrading our AS2 solution (including the AS2 certificate) and will begin migrating OrderStream users to the new solution starting February 2025.

Here’s a preview of the tasks that must be completed for the migration.

Before your migration date

- If your AS2 client software does not support Server Name Indication (SNI) headers, refer to the SNI Header section below for more information.
- If you use IBM iSeries with ZMOD AS2 software, reach out to Software Support for further guidance.
- If you maintain multiple AS2 connections to the Rithum platform, reach out to Software Support to confirm the AS2 connections being migrated.
- If you’re able to migrate to the new AS2 solution ahead of the designated date and time, reach out to Software Support to let us know and we’ll schedule your migration date.

On your migration date

1. Update the Endpoint URLs and the Rithum AS2 IDs to the updated AS2 details. See the Configuration Settings section below. You cannot update your Endpoint URLs and Rithum AS2 IDs for Rithum before your migration date.

2. Download the updated AS2 certificates. You cannot update your AS2 certificate before your migration date.

3. If you whitelist IP addresses as part of your security protocol with your AS2 client, you’ll need to update your firewall settings to allow connections to/from Rithum systems.

Failure to make these updates by your migration date will disrupt your ability to communicate with Rithum.

Recommended Connection Settings

• Asynchronous Connection
• TLS v1.3 Enabled

Minimum Connection Requirements

Environment Details

Production

Endpoint URL: HTTPS://as2.rithum.com/us/receive
Note: This Endpoint URL requires HTTPS with TLS v1.2+ connections

Asynchronous MDN Endpoint URL:
If you intend to use an asynchronous connection, send MDNs to:
HTTPS://as2.rithum.com/us/receive/mdn
Note: We recommend that you send your asynchronous MDN to the URL within 5 minutes of receiving the file. After 5 minutes, the transfer will be considered failed.

Port: 443

Static IP Pool:
• 3.227.140.114
• 54.225.3.225
• 3.224.250.206
• 44.236.75.232
• 52.42.144.200
• 52.39.18.225

Rithum AS2 ID: RITHUMAS2

SNI Header Requirement

Server Name Indication (SNI) is an extension to the TLS protocol that allows the client to specify the hostname it is trying to connect to at the start of the handshake process. This is crucial for the Rithum platform, as it leverages AWS CloudFront for enhanced edge performance and global reach. SNI enables Rithum to serve multiple secure (SSL/TLS) websites from the same IP address, ensuring efficient and secure data transmission.

Action required:
1. Verify SNI Support. Please check with your AS2 client software provider or your IT department to ensure that your AS2 client supports SNI headers.
2. Upgrade if Necessary. If your AS2 client does not support SNI, an upgrade will be required. We recommend you contact your software vendor for the necessary updates or patches. If you’re unable to upgrade your AS2 software, you may be interested in other integration options. Visit HubHelp to learn about your connection options.
3. Test Connectivity. After confirming SNI support, please reach out to Software Support if you would like to test the new connection. We can confirm that both you and Rithum are able to send and receive messages from the new server.

If you have any questions or need help verifying SNI support, reach out to Software Support.