Trading Partners
Trading partners represent the external organizations you exchange AS2 messages with. Each partner has a unique AS2 ID that identifies them in the AS2 protocol.
Partner List
The Partner list shows all your configured trading partners. Click "+ Create Partner" to add a new trading partner:
Creating a Partner
Click "+ Create Partner" from the Partner List to open the Create Partner form:
Partner Fields
| Field | Required | Description |
|---|---|---|
partner_as2_id |
Yes | The unique AS2 identifier for this partner. Must match what the partner uses in their AS2 configuration. |
partner_name |
Yes | A human-readable name for the partner (for display purposes). |
partner_as2_alias |
Yes | The certificate alias used to identify and retrieve the partner's public certificate from the keystore. This alias is used when encrypting outbound messages and verifying signed MDN responses. When you upload a partner's certificate on the Certificate page, this alias is automatically suggested as the certificate entry name. |
partner_email |
Yes | Contact email for the partner. |
status |
No | Enable or disable this partner. Disabled partners cannot be used in partnerships. |
The partner_as2_id must exactly match the AS2 ID your trading partner uses. Contact your partner to get their correct AS2 ID before creating the partner entry.
The partner_as2_alias field is the keystore alias that links this partner to their X.509 certificate. When you create a Certificate for a partnership:
- The alias field is automatically populated from the partner's
partner_as2_aliasvalue - The partner's public certificate is stored in the keystore using this alias
- When sending messages, the system uses this alias to retrieve the partner's certificate for encryption
- When receiving MDN responses, this alias is used to verify the partner's signature
Make sure to use a consistent, meaningful alias (e.g., the partner's company name or AS2 ID) for easier certificate management.
Next Steps
After creating a trading partner, you'll need to set up Certificates for encryption and signing. Then create a Partnership to define how messages are exchanged.