Certificate rotation between two companies
Mutual TLS is easy until the certificate belongs to someone else's change process. The overlap window, the trust-store split, and the alert that has to exist.
Notes / Secure integration
Almost nobody writes about WS-Security, mutual TLS or hardware security module file ingestion, because that work only exists inside banks and payment companies. These notes come from building it in production: what the specifications leave undefined, what breaks between two organizations, and what the runbook has to say.
Mutual TLS is easy until the certificate belongs to someone else's change process. The overlap window, the trust-store split, and the alert that has to exist.
The libraries, the JAXB removal, the XML signature pitfalls and the canonicalization details that decide whether a WS-Security message verifies or silently fails.
How to ingest encrypted files from a hardware security module over SOAP in Spring Boot 3.5, secured with mutual TLS and WS-Security, and processed idempotently.