Architecture component overview
Last updated
Last updated
The image below depicts the Architecture of the DSS API services.
In this image there are various components which are described below.
The DSS API Service is a service which provides functionalities such as document signing, timestamping and validation. The DSS API has been updated in terms of:
service functionality
validation templates and process
property exposure for digital signing
This service hosts both an API and a web interface.
The API is used by the SimpleSign application to provide document signature capabilities.
The User Interface can be used to validate signatures and certificates and get detailed reporting on the validation.
The Service can run locally on a user's machine, on-premise of in a kubernetes environment.
The DSS API Utilities service is a service which provides additional functionalities. One of these functionalities is PDF/A validation. This feature is also used in the SimpleSign application to provide PDF/A validation on uploaded documents.
SimpleSign is a native application which provides a User Interface which enables the user to upload, view and sign documents.
The Trust1Connector is a technical local service that aims to make all hardware devices and tokens, used for authentication and digital signing, interoperable in a web environment. No operating system dependencies to take into account, no browser dependencies, and compatible with smart-card readers, contactless readers and pin-pad readers/terminals. The Trust1Connector provides you with a secured communication channel between your local device and a web browser.
The goal of the Trust1Connector is enabling secured communication, from a (web) application, to a desktop device, in the world of personal or device identity, mainly for the following use cases:
Read token information (personal info, ICAO, ...)
Read certificates, certificate chains or certificate information
Verify a known password (PIN, PUK, CAN, ...)
Authenticate using a hash
Digitally sign a hash
Validate digitally signed hashes
These use-cases are used by the SimpleSign application to provide the end-user the capabilities to sign documents with their local smart cards or tokens