Overview
SDK Access Point sends and receives AS4 messages and connects to a separately deployed message system.
Connect your message system to the transport used by Sweden’s Säker digital kommunikation (SDK). SDK Access Point carries AS4 messages between organizations. Run it as a standalone service with its own configuration, certificates and PostgreSQL schema, while your message system handles users and business workflows. How the access point fits into Digg’s SDK federation
What you can do
Section titled “What you can do”- Fit the access point into your existing environment. Deploy the transport service separately and integrate your message system through a private, tenant-bound API.
- Follow a delivery across the transport boundary. Use transport status, signed AS4 receipts and a persistent transfer journal to see what the access points recorded.
- Rehearse the exchange before onboarding. Use the closed Docker test profile to send and retrieve a synthetic message, inspect receipts and check recovery.
How the access point connects
Section titled “How the access point connects”| Boundary | Role |
|---|---|
| Public AS4 listener | Exchanges messages and signed transport receipts with other access points. |
| Private Interface C listener | Accepts submissions, exposes transport status and lets the message system retrieve inbound packages. It uses mutual TLS (mTLS) scoped to the tenant. |
| PostgreSQL | Stores access point transport state, inbound packages, transfer history and signed receipt evidence. |
Start here
Section titled “Start here”- Architecture and security model follows a message across both listeners and the database.
- Installation covers the Docker delivery and Windows host preparation.
- Configuration shows how to set ports, database roles, certificates and secret files. Runtime settings lists the listener and routing options.
- Integration describes the private package API and the different acknowledgements.
- Operations covers health checks, structured logging and audit and recovery.