Generated page. Written from IdaMilk/Suntado_OpenAS2 at commit 21d550f on 2026-07-28. Partner identifiers and endpoint URLs are deliberately not reproduced here, per the wiki's redaction policy.
Suntado OpenAS2
What is it?
Configuration — not code. This repository holds the OpenAS2 config that defines who Suntado exchanges EDI files with, how those exchanges are secured, and where files are picked up and delivered.
OpenAS2 is a Java implementation of AS2, the B2B protocol used to move EDI documents over HTTP with signing, encryption and signed receipts. It is stateless: all behaviour comes from its config files, which is exactly why they belong in git.
Purpose
The README puts the case better than a summary would: without version control, one wrong XML attribute — a mistaken AS2 ID, certificate alias or endpoint URL — can silently break file delivery with no audit trail.
Keeping the config here provides:
- Version control so partner changes are tracked, auditable and reversible
- Drift prevention between environments and after server restores
- Partner onboarding by pull request, with a review step before live EDI changes
- Documentation of the AS2 relationships Suntado maintains
- Backup of config that, if lost, would break live flows
How it Works
partnerships.xml is the core file, defining two things:
Partners — each participant, Suntado included, with an AS2 identifier and the certificate alias used to sign or verify its messages.
Partnerships — the directional pairing between two partners, carrying the sender, receiver, endpoint URL, encryption and signing algorithms, receipt (MDN) settings, and the directories where files are collected and delivered.
A partnership is directional. Sending to a partner and receiving from them are two separate entries, and they can differ in algorithm or endpoint.
certs/ holds partner public certificates in .cer form:
| Certificate | Party |
|---|---|
suntado.cer | Suntado's own public certificate |
westrocktest.cer | WestRock, test environment |
wowlogistics.cer | WOW Logistics |
These are public certificates — safe to commit, and required by both sides to verify signatures. Private keys and the keystore are not in this repository and must be supplied on the server.
Where it sits
AS2 is one of several transports Suntado EDI can use — its v2.0 architecture selects SFTP, API or AS2 per partner. The two systems are coupled only by directories on disk: EDI writes a file, OpenAS2 picks it up and delivers it, and inbound files arrive the same way in reverse.
Operations
A .github/workflows/deploy.yml pushes configuration to the OpenAS2 server, so the repository is the source of truth rather than a copy — an improvement on the manual round trip used by the NetSuite repositories.
Onboarding a partner is: obtain and commit their public certificate, add a <partner> entry, add the two directional <partnership> entries, open a pull request, deploy. Exchanging test messages before enabling production traffic is the norm — the presence of westrocktest.cer shows that practice in use.
When delivery fails, the useful signals are OpenAS2's own logs and whether an MDN came back: no MDN generally means a transport or certificate problem, whereas a negative MDN means the partner received the message and rejected it.
Repository
| Repository | IdaMilk/Suntado_OpenAS2 |
| Primary language | XML (configuration) |
| Files | 9 |
| Last activity | 2026-06-03 |
| Status | Active |
The README is thorough and explains the why as well as the what — a good model for the repositories that have none.