This document ESYA provides an introductory summary on how to use ESYA CMS Signature API. With CMS Signature API you can manage your keys with smartcards, validate certificates, create and verify electronic signatures. API requires a valid license.
You need a digital certificate and a secure container for the private key in order to create signature. Usually smartcards are used as the secure container for the private keys. For detailed information about signature creation please refer to the section Signature Creation .
Signature verification consists of certificate validation , cryptographic verification of the signature and structural validation of the signed document. Certificate validation requires a validation policy file which is an XML file coming with the API and can be configured as desired. Please refer to the section Signature Verification for more information.
E-Signature API requires the license file, certificate validation policy file and certificate store file. To create qualified signatures, hardware security devices are needed. Generally smartcards are used for this purpose. Using smartcards requires the drivers of the smartcard and smartcard reader.A smartcard card viewer utility program to view the contents of the smartcard can be obtained from a smartcard manufacturer.
For a quick start see the section Quick Start.
API supports the signature types documented in ETSI TS 101 733 listed below:
ETSI TS 101 733 includes detailed information about the signature types listed above. Here they are explained briefly. The figures are from ETSI TS 101 733 document.
Creating Different Signature Types