Enable AS2 Connections

With the 23R3 release, Veeva Safety AS2 Connections replace Safety Gateways. AS2 Connections provide significant technical improvements including Admin management of Internet Protocol (IP) lists, more concise outbound IP lists, and improved Certificate Management.

Complete the steps in the following sections to enable AS2 Connections in your Vault.

Updates

We have added the following updates to this feature:

  • With the 25R2 release, Safety introduces the ability to create a Sponsor certificate within Vault for use with an AS2 Connection.
  • With the 25R1 release, Safety introduces:
    • AS2 Connection: Uncompressed Request Setting: When enabled, Vault replaces the Compress Before Sign field on the AS2 Connection object with an AS2 Compression Settings field.
    • AS2 Connection: ACK on MDN URL Setting: When enabled, Vault introduces an ACK on MDN URL setting to accommodate AS2 partners who send their ACK messages using the same URL as the MDN.
  • With the 24R2 release, Vault introduces:

Create the AS2 Layout

Copy the standard layout for the Connection object with the AS2 object type and set the new custom layout as the default.

Update the Transmission Profile Layouts

Add the Connection field to the Details section of the following Transmission Profile layouts:

  • AS2 Gateway Detail Page Layout
  • System Gateway Detail Page Layout

(24R2) Configure AS2 Connection Troubleshooting Tools

With the 24R2 release, Vault provides the following tools to troubleshoot AS2 Connection issues:

  • Send an existing test file to a destination to check if the connection is successful. This eliminates the need to generate a compliant Case to test the AS2 Connection with a partner or health authority.
  • View the latest blocked IP addresses that are not on the Connection Allowed list that the destination used to send the AS2 request to Vault.

For more information, see Troubleshoot AS2 Connections.

Add Transmission Layout

Complete the following steps to create a Test Transmission layout from the standard Veeva layout:

  1. Go to Admin > Configuration > Objects > Transmission > Layouts.
  2. On the Test Transmission Detail Page Layout, select Save As from the Actions menu.
  3. In the Save As window, select Done.
  4. On the Transmission: Record Name page, update fields and sections if needed and then select Save.

Add the Send Rejected Inbound IPs Notification User Action

Complete the following steps to add the user action to the AS2 Connection object:

  1. Go to Admin > Configuration > Objects > Connection > Actions.
  2. Select Create.
  3. In the Create Action window, select Send Rejected Inbound IPs Notification and then select Continue.
  4. Select the Available in All Lifecycle States checkbox.
  5. On the Atomic Action Security Defaults dialog, adjust the default action settings for each lifecycle state if needed, and then select Save.

(24R2) Configure Static IPs for AS2 Vault URLs in AS2 Connections

Prior to the 24R2 release, Vault supported the use of Domain Names when specifying the AS2 Vault URL field of an AS2 Connection. With the 24R2 release, Vault also supports the option to use static IP addresses for this field. This is intended for recipients who specify the use of static IP addresses instead of Domain Names. For more information on configuring Vault for such recipients, see the descriptions of the AS2 Vault Domain / IP Configuration and AS2 Ingress IPs fields on the applicable AS2 Connection configuration page (see AS2 Connections Overview).

Update the AS2 Connection Layout

To update the AS2 Detail Page Layout of the AS2 object layout, in the AS2 Sponsor Details section, add the following fields:

  • AS2 Vault Domain / IP Configuration
  • AS2 Ingress IPs

(25R1) Configure AS2 Connection: Uncompressed Request Setting

With the 25R1 release, Vault replaces the Compress Before Sign field on the AS2 Connection object with an AS2 Compression Settings field. This new field includes the option of sending AS2 messages uncompressed for agencies and partners that specify this requirement.

In Vaults provisioned before the 25R1 release:

  • Vault migrated the value in the Compress Before Sign field on all AS2 Connections to the AS2 Compression Settings field.
  • Vault removed the Compress Before Sign field from all layouts.

After you have configured this feature, see Custom AS2 Connections for more information on the AS2 Compression Settings field.

Update the AS2 Connection Layout

To update the AS2 Detail Page Layout of the Connection object layout, in the AS2 Details section, add the AS2 Compression Settings field.

(25R1) Configure AS2 Connection: ACK on MDN URL Setting

With the 25R1 release, Vault introduces a new AS2 Connection object setting to accommodate AS2 partners who send their ACK messages using the same URL as the MDN.

After you have configured this feature, see Custom AS2 Connections for more information on the AS2 Partner Sends ACK on MDN URL field.

Update the AS2 Layout

To update the AS2 Detail Page Layout of the Connection object layout, in the AS2 Details section, add the AS2 Partner Sends ACK on MDN URL field.

(25R2) AS2 Connection: Sponsor Certificate Generation

With the 25R2 release, Veeva Safety introduces the ability to create a Sponsor certificate within Vault for use with an AS2 Connection. Previously, these certificates had to be created outside of Vault. Alternatively, you can continue to upload a Sponsor Certificate for an AS2 Connection that was created outside of Vault. After creating or uploading a Sponsor Certificate, you can download the Public Sponsor Certificate for sharing with the Partner associated with the connection.

Update the AS2 Layout

To update the AS2 Detail Page Layout of the Connection object layout:

  • In the AS2 Partner Details section, add the AS2 Partner Certificate Serial Number field.
  • In the AS2 Sponsor Details section, add the AS2 Vault Certificate Serial Number field.