Remote signing using the SCAL2 and ILM Signing is possible by integrating the SAM and the signing back-end of the remote signing solution. We call it SAMCryptoToken. It is a special implementation of the CryptoToken for the signing component, which contains necessary functions and interfaces to communicate with the SAM and the user’s device.
SAMCryptoToken integration architecture
The signing component requests SAD through the signing back-end. The SIC exchanges SAD and DTBS with the SAM using SAP, while signing requests and signature values use separate routes.
SAMCryptoToken integration architectureRead components, boundaries and directed exchanges
The signing component requests SAD through the signing back-end. The SIC exchanges SAD and DTBS with the SAM using SAP, while signing requests and signature values use separate routes.
Signing → Signing logic / signing back-end: SAD request
Signing logic / signing back-end → User interface: SAD request
User interface → Signing: Signing request
SAM (Signature Activation Module) → Signing: Signature value
SIC (Signer Interaction Component) ↔ SAM (Signature Activation Module): SAP (Signature Activation Protocol); SAD (Signature Activation Data); DTBS (Data To Be Signed)
Arrows show exchange direction; double-headed arrows show exchanges in both directions. The SAP band carries SAD and DTBS between the SIC and SAM. The band represents an exchange, not an additional environment boundary.
What is happening when user would like to sign the data within the context of the signing component and SCAL2? The typical signature process is as follows:
Request to sign the data is triggered from the the client
Signer prepares the Data To Be Signed and asks the signing back-end to confirm by the user
User confirms the Data To Be Signed and activates the private key for the signing operation
QSCD + SAM verifies the request and produces the signature
Signer completes the operation and provides the result