# 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.


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: 
Once you have enabled this feature in your Vault, we recommend replacing any Custom AS2 Gateways in your Vault with an equivalent Custom AS2 Connection. See <a href="/en/lr/01460/">Replace a Gateway Profile with an AS2 Connection</a> for instructions on how to do this.</p>
    </div>
  </div>
</div>



### Updates

We have added the following updates to this feature:

* With the 25R2 release, Safety introduces the ability to [create a Sponsor certificate][5] 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_][3] field.
  * **AS2 Connection: ACK on MDN URL Setting**: When enabled, Vault introduces an [ACK on MDN URL][4] setting to accommodate AS2 partners who send their ACK messages using the same URL as the MDN.
* With the 24R2 release, Vault introduces:
  * **AS2 Connection Troubleshooting Tools**: Vault provides the tools to [troubleshoot _AS2 Connection_ issues][1].
  * **Static IPs for AS2 Vault URLs in AS2 Connections**: Vault supports using [static IP addresses][2] when specifying the _AS2 Vault URL_ field of an _AS2 Connection_.

## Create the AS2 Layout


<a href="/en/lr/26387/#save-as-layout">Copy</a>
the standard layout for the _Connection_ object with the _AS2_ object type and set the new custom layout as the <a href="/en/lr/26387/#set-a-default-layout">default</a>.

## Update the Transmission Profile Layouts

<a href="/en/lr/26387/#how-to-add-object-fields">Add</a> 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 {#r242-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 <a href="/en/lr/728014/">Troubleshoot AS2 Connections</a>.

## 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 {#r242-static-ips-as2-vault-urls}

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 <a href="/en/lr/703946/#supported-agencies">AS2 Connections Overview</a>).

### Update the AS2 Connection Layout

To update the _AS2 Detail Page Layout_ of the _AS2_ object layout, in the _AS2 Sponsor Details_ section, <a href="/en/lr/26387/#how-to-add-object-fields">add</a> the following fields:

* **AS2 Vault Domain / IP Configuration**
* **AS2 Ingress IPs**

## (25R1) Configure AS2 Connection: Uncompressed Request Setting {#r251-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 <a href="/en/lr/01458/#as2-compression-settings">Custom AS2 Connections</a> 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, <a href="/en/lr/26387/#how-to-add-object-fields">add</a> the **AS2 Compression Settings** field.

## (25R1) Configure AS2 Connection: ACK on MDN URL Setting {#r251-ack-on-mdn-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 <a href="/en/lr/01458/#partner-ack-on-mdn-url">Custom AS2 Connections</a> 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, <a href="/en/lr/26387/#how-to-add-object-fields">add</a> the **AS2 Partner Sends ACK on MDN URL** field.

## (25R2) AS2 Connection: Sponsor Certificate Generation {#r252-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, <a href="/en/lr/26387/#how-to-add-object-fields">add</a> the **AS2 Partner Certificate Serial Number** field.
* In the _AS2 Sponsor Details_ section, <a href="/en/lr/26387/#how-to-add-object-fields">add</a> the **AS2 Vault Certificate Serial Number** field.

[1]: #r242-troubleshooting-tools
[2]: #r242-static-ips-as2-vault-urls
[3]: #r251-uncompressed-request-setting
[4]: #r251-ack-on-mdn-setting
[5]: #r252-sponsor-certificate-generation