E-diplomas: a secure path from XML to registration
One of the most demanding delivery topics was the e-diploma flow: the XML document, signing, external services and asynchronous status checks had to form one predictable process.
INTEGRATION
REST and SOAP meet in one process
I prepared a communication layer with Java, Spring Boot, Apache CXF and WSS4J. It handled templates, documents, signed packages, OAuth-protected REST calls and statuses returned by RDE and POL-on.
CRYPTOGRAPHY
Two signatures, two different responsibilities
I kept the XML document's XAdES signature separate from SOAP WS-Security signing and encryption. That meant treating canonicalisation, references, certificates and roles as distinct concerns.
.NET LAYER
The private key stays on the token
In C# and .NET I prepared an API for batch signing, certificate handling and result reporting. RSA operations were delegated to a card or cryptographic token through PKCS#11; isolated SoftHSM made technical tests possible without using a qualified signature.
DOCUMENTATION AND OPERATIONS
Knowledge first, automation second
I analysed WSDL, XSD, OpenAPI and sample messages, then turned the findings into an organised knowledge base and diagnostic tools. The public version intentionally omits identifiers, service addresses, secrets and configuration details.