Die einfachste API zum Signieren, Zertifizieren und Verifizieren

CLI integration example code

Die Entwickler Dokumentation ist momentan nur auf Englisch verfügbar.

Von Entwicklern, für Entwickler

Wählen Sie die optimale Integrationslösung für Ihre Architektur

Implementieren Sie unsere lokale API in einer VM oder einem Docker-Container in Ihrer Infrastruktur

Nutzen Sie einfach unsere API, um Ihre Software um die Signatur und Verifizierung von Dokumenten zu erweitern

Verwenden Sie unseren CLI-Client zum Signieren und Verifizieren von Dokumenten über die Befehlszeile

Integrieren Sie Certifaction einfach in Ihre Software und erstellen Sie schnell und automatisch Signaturen – auf jeder Plattform und in jeder Skriptsprache

How to sign and certify within your IT landscape

Overview of the full integration process

One

Choose the right integration solution for your architecture

The Certifaction CLI can be used in two modes:

  • Interactive to execute commands on the shell, as part of a script or from a third party application.
  • Server mode that exposes HTTP endpoints.

In both cases, the CLI sits between the third party application and Certifaction API and will handle document signing, verification and revocation without leaking the document content outside the controlled IT infrastructure of the client.

Overview: Integration with Certifaction CLI

Standalone application integration

In this scenario, the standalone application will use the OS command execution available to their platform to run the Certifaction commands. The documents can either be saved and loaded on the file system, or they can be passed to the command using the standard input and output.
Certifaction Standalone application integration

Running the HTTP server on a node

In this scenario, the Certifaction CLI is started in server mode, either directly in a node or VM, or inside a Docker container. The client will use HTTP to sign and verify documents with the guarantee that documents do not leave the client IT system. This is the best option for centralized document signature where documents are signed during an automated document workflow.
Two

Simple document signature

Here are the steps during a simple document signature:

  1. The CLI Receives the PDF document to sign and process it (add security features including a unique secure URL and one or more signature pages).
  2. The hash of the file is sent to Certifaction API for signature
  3. Certifaction API uses one of its pluggable signature provider depending on the signature level and jurisdiction
  4. Certifaction API returns the PKCS #7 CMS signature to the CLI
  5. The CLI embeds the signature in the PDF document and returns to the Client

Additional signatures can be appended to an already signed document sequentially. Sending a signed document to an other signer is a simple and valid option.

Three

Document Digital Twin

In addition to storing the secure URL inside the PDF as custom information. A Digital Twin QR code can be added to the document. This QR code contains the secure URL that can be used to retrieve the encrypted version of document stored in Certifaction servers.

When printing the document, the visible QR code can be scanned to retrieve the last version of the document. Certifaction Digital Twin bridges the world of printed and digital documents.

Here are the steps to store an encrypted version of the document and return a Digital Twin URL:

  1. Before signature, a unique and secure URL created and added to the document with a QR code
  2. The document is encrypted
  3. The encrypted copy is stored in Certifaction Digital Archive (DA)
  4. The Digital Twin URL is recorded in Certifaction document locator

Ihr Weg in die Zukunft

Schliessen Sie sich führenden Organisationen an

Kontaktieren Sie uns jetzt und erfahren Sie, wie wir Ihre Firma dabei unterstützen können, Ihre Signier-, Zertifizier- und Verifizierprozesse digital, intuitiv und zukunftssicher zu machen.

emonitor Logo
emonitor Logo