Skip to content

Fortified IDDocs

Architecture and security model

Follow an AS4 delivery through the access point and see where transport, authentication, keys and data are handled.

SDK Access Point is an independently deployed phase4 service. It joins the message system’s private network to the AS4 transport boundary and keeps its own transport state in PostgreSQL.

Interface Paths Identity and responsibility
AS4 peer listener /as4 Peers authenticate with mutual TLS. The access point also evaluates the AS4 message signature and checks that it matches the sending party.
Private Interface C listener /transport/*, /health/* Uses a separate internal client CA. Transport API calls require the bearer credential for the tenant identified by the client certificate. Health uses a private diagnostic client identity.
PostgreSQL JDBC connection from the runtime and migration process The runtime reads and records transfer state under a restricted login. An operator uses a separate login for schema changes.

In split-listener mode, the AS4 listener serves only /as4. Keep Interface C on the private network and use separate trust material for the two listeners. The process is configured for one tenant, and its private operations are scoped to that tenant. Runtime settings · Key management and PKI

  1. The message system submits an XHE (Exchange Header Envelope) package over Interface C with an idempotency key. The access point validates the envelope and routing metadata.
  2. The access point selects the peer endpoint and certificate. With dynamic routing enabled, it looks up the peer through SML and verifies signed SMP metadata.
  3. The access point records the dispatch in PostgreSQL before the wire attempt. It signs and encrypts the AS4 exchange, then validates the peer’s signed transport receipt before recording acknowledgement.
  4. The message system queries transport status using the returned transport ID. If a temporary failure is eligible for retry, the access point claims the stored dispatch and attempts delivery again. The default AS4 profile schedules up to four resends after the first attempt, at three-minute intervals within a twelve-minute window. Package API · Recovery diagnostics

The access point validates the peer’s AS4 request and the recipient before storing the original XHE package for the receiving tenant. A byte-equivalent retry with the same AS4 message ID and sender receives a transport receipt without creating another inbox entry. Conflicting content under the same identity is rejected. The message system retrieves the stored bytes through Interface C and acknowledges retrieval after it has processed or durably stored the package.

The access point decrypts the AS4 transport layer. A payload encrypted end to end between message systems stays opaque to the access point. An application response, such as an SDK message acknowledgement, is exchanged as a separate package. SDK and Digg · Interpret acknowledgements