Key management and PKI
Configure AS4 message keys, PKCS#11 tokens, listener credentials, trust anchors and certificate revocation.
Keep the AS4 message key and the TLS identities separate. Each identity has a different purpose, and each listener has its own trust configuration.
Certificate and key roles
Section titled “Certificate and key roles”| Role | Where it is configured | Purpose |
|---|---|---|
| Public AS4 TLS | tls.keystore.*, tls.truststore.* and tls.key.alias |
Presents the access point’s transport identity and authenticates peer connections. |
| Private Interface C TLS | internal-tls.properties |
Presents the private server identity and authenticates clients using the internal CA. |
| AS4 message key | message.keystore.* and message.key.alias |
Signs AS4 messages and receipts, and unwraps the symmetric key used for inbound AS4 decryption. |
| AS4 message trust | message.truststore.*, recipient.key.alias and root.alias |
Loads public recipient and trust anchor certificates from the configured store. With dynamic routing, signed SMP metadata supplies the destination certificate. |
| Readiness client | health.properties |
Supplies a separate client identity and server trust for private health checks. |
Select an AS4 message keystore
Section titled “Select an AS4 message keystore”For a file-backed key, use message.keystore.type=PKCS12 and set message.keystore.path to the PKCS#12 store. For a hardware security module (HSM) or another PKCS#11 token, configure the provider for the runtime process:
message.keystore.type=PKCS11message.pkcs11.configuration=/etc/sdk-access-point/pkcs11.cfgmessage.key.alias=as4-message-keymessage.keystore.password.env=AP_MESSAGE_KEYSTORE_PASSWORDThe provider file points to the vendor’s PKCS#11 library and the intended token or slot. Use an RSA key alias with its certificate chain, provide the token PIN through the named secret reference, and retain the separate message truststore configuration. The runtime uses a key handle for private-key operations. For a container, the provider configuration and native client library must be accessible inside the runtime environment.
Configure certificate trust and revocation
Section titled “Configure certificate trust and revocation”AP_PKI_CONFIG identifies a properties file with separate realms for as4, tls, smp and internal. Set the applicable CA anchors, intermediate certificates and certificate revocation list (CRL) URLs using the .anchors, .intermediates and .crls keys for each realm. Use CA certificates as anchors and distinct CA keys for public and internal TLS.
Use the issuer’s current CRL URLs. The policy checks the signed CRLs for issuer, validity and revocation. If certificate status cannot be established under the configured policy, the access point denies the affected operation. Check CA chains, CRL reachability and the host clock when diagnosing certificate failures.
Rotate certificates
Section titled “Rotate certificates”Inventory the TLS, AS4, readiness and trust material for each environment. Prepare the new certificates and any updated CA or CRL references before changing the instance. Coordinate peer metadata changes for AS4 certificates, then check private readiness and run a send-and-receive exchange after the change. SDK and Digg references · Logging and audit