Technical Reference

Security & Certificate Management

How signing keys, partner certificates, and per-message cryptography are managed.

Every message Archr.Hermod sends is signed with your private key and, where the partnership calls for it, encrypted to the partner's public certificate. Every message Archr.Hermod receives has its signature verified against that partner's certificate before it's accepted. This applies uniformly across all three protocols — ebMS uses XML digital signatures and XML encryption, AS2 uses S/MIME, and SFRM uses CMS/PKCS#7 — the security guarantee is the same even though the wire format differs.

Key management

Certificates and keys are managed centrally rather than as files scattered across a filesystem: your own signing certificate, and each trading partner's public certificate used to encrypt outbound messages and verify inbound signatures. Since private keys are very sensitive, they are encrypted. Certificate metadata — subject, serial number, validity window — is tracked automatically, so an expiring partner certificate is something you're warned about, not something that breaks delivery without warning.

← Back to the technical reference