# EDI AS2 Connection Parameters Request Template

> Source: https://netray.co/tools/edi-as2-connection-parameters-request-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A form to exchange AS2 IDs, endpoints, certificates, MDN settings and security options with a trading partner before testing.

## Category

developer

## Audience

- EDI coordinator
- Integration engineer
- Network administrator

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Your company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Trading partner

**Key:** partner

**Type:** text

**Default:** Northwind Retail

#### Our AS2 ID

**Key:** our_as2id

**Type:** text

**Default:** ACMEPRECISION

#### Partner AS2 ID

**Key:** their_as2id

**Type:** text

**Default:** NORTHWINDEDI

#### Our AS2 receive URL

**Key:** our_url

**Type:** text

**Default:** https://as2.acme.example:4080/as2/receive

#### Partner AS2 receive URL

**Key:** their_url

**Type:** text

**Default:** https://as2.northwind.example/as2/inbound

#### Message signing

**Key:** sign

**Type:** select

**Options:**

- SHA-256
- SHA-1
- SHA-384
- SHA-512
- None

**Default:** SHA-256

#### Encryption

**Key:** encrypt

**Type:** select

**Options:**

- AES-256
- AES-128
- 3DES
- None

**Default:** AES-256

#### MDN type

**Key:** mdn

**Type:** select

**Options:**

- Synchronous signed
- Asynchronous signed
- Synchronous unsigned
- None

**Default:** Synchronous signed

#### Compression

**Key:** compress

**Type:** select

**Options:**

- None
- ZLIB

**Default:** None

#### Our certificate expiry

**Key:** cert_exp

**Type:** date

**Default:** 2027-09-30

#### Source IP addresses to allow

**Key:** ips

**Type:** textarea

**Default:** 203.0.113.10
203.0.113.11

#### Technical contact

**Key:** contact

**Type:** text

**Default:** Rahul Mehta, edi@acme.example, +1 555 0100

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-20

**Blocks:**

#### AS2 Connection Parameters

**Body:** Prepared by: {{company}}
Trading partner: {{partner}}
Date: {{date}}

#### Identifiers and endpoints

**Table:**

**Columns:**

- Parameter
- Our value
- Partner value

**Rows:**

**0:** AS2 ID

**1:** {{our_as2id}}

**2:** {{their_as2id}}

**0:** Receive URL

**1:** {{our_url}}

**2:** {{their_url}}

**0:** Technical contact

**1:** {{contact}}

**0:** Emergency contact

#### Security and message options

**Table:**

**Columns:**

- Option
- Agreed setting

**Rows:**

**0:** Signing algorithm

**1:** {{sign}}

**0:** Encryption algorithm

**1:** {{encrypt}}

**0:** MDN receipt

**1:** {{mdn}}

**0:** Compression

**1:** {{compress}}

**0:** Content type

**1:** application/edi-x12 or application/edifact

**0:** TLS version

**1:** TLS 1.2 or higher

**0:** Filename in header

#### Certificates

**Body:** Our public certificate expires: {{cert_exp}}

Exchange public certificates only, never private keys. Confirm the signing certificate, the encryption certificate and any intermediate certificates. Agree on a renewal notice period so both sides can update before expiry.

#### Network access

**Body:** Source IP addresses that will connect to the partner:
{{ips}}

Partner source IP addresses to allow on our firewall:
(to be provided by partner)

#### Test and go-live

**Table:**

**Columns:**

- Step
- Owner
- Date
- Done

**Rows:**

**0:** Exchange certificates

**0:** Connectivity test

**0:** Signed and encrypted test file

**0:** MDN received and verified

**0:** Production cutover

#### Approvals

**Signatures:**

- Our EDI coordinator
- Partner EDI contact

**Notes:** This form records agreed settings only. Exchange certificates through a secure channel and never send private keys or passwords on this form. Confirm algorithms against your own security policy and the partner's guide.

## Content

**Intro:** Before any EDI file moves over AS2, both sides must agree on identifiers, URLs, certificates and security options. A single wrong AS2 ID or an expired certificate stops the connection. This form collects every parameter in one document you can send to the partner and file afterwards.

**Sections:**

#### How to use the form

**Body:** Fill in your own values, export to PDF or Word and send it to the partner's technical contact, asking them to complete the second column. AS2 IDs are case sensitive in many products, so copy them exactly. Agree on signing, encryption and MDN type before testing, because mismatches show up as vague decryption or verification failures. Use the test and go-live table to track who does what.

**Bullets:**

- AS2-From and AS2-To must match each side's configuration exactly
- Decide synchronous or asynchronous MDN before testing
- Record certificate expiry dates and set reminders

#### What each parameter does

**Body:** The AS2 ID identifies each partner in the message headers. The receive URL is where the other side posts messages. Signing proves the sender and integrity, encryption protects content in transit, and the MDN is the receipt that confirms the message arrived and, if signed, was not altered. SHA-256 and AES are the usual modern choices, while SHA-1 and 3DES remain only for legacy partners. TLS on the transport is a separate layer.

#### Certificate management

**Body:** Expired certificates are the most common cause of sudden AS2 outages. Put every certificate expiry into a shared calendar at least 60 days ahead. Agree how renewals are exchanged and whether the partner supports two active certificates during a changeover. Public certificates only should ever travel by email or portal. Store private keys in your integration platform's key store with restricted access.

#### Common mistakes

**Body:** Wrong IP allow lists, a firewall that blocks the inbound port, mismatched MDN modes and sending the wrong certificate (signing instead of encryption) cause most failed first tests. Another is forgetting that load balancers can alter source addresses. Test with a small file first, then with a realistic one.

**Cta:** Netray can help review your integration platform's AS2 setup and certificate calendar if your partner connections are managed ad hoc.

**Faq:**

#### What is an AS2 ID?

**Answer:** It is the name each party uses to identify itself in AS2-From and AS2-To message headers. IDs are agreed between partners, are often case sensitive and should be unique for each trading relationship.

#### What is an MDN in AS2?

**Answer:** A Message Disposition Notification is the receipt returned after a message is received and processed. It can be signed to prove the content arrived intact. Sync MDNs return on the same connection, async MDNs return later to a separate URL.

#### Which hash and encryption should I choose?

**Answer:** Choose what your partner supports from the stronger options, typically SHA-256 for signing and AES-128 or AES-256 for encryption. Avoid SHA-1 and 3DES unless a legacy partner insists, and follow your security policy.

#### Can I send private keys with this form?

**Answer:** No. Only public certificates should be exchanged. Private keys must stay inside your own key store and never travel by email, chat or forms.

## Search terms

as2 connection setup form, as2 parameters template, as2 trading partner information sheet, as2 id certificate exchange, edi as2 onboarding form, as2 mdn settings, as2 setup checklist

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json