Remote service of a provider
Signing · Provider API
Connectors
The services the product connects to, grouped by what they do.
Each connector carries one of the same three states as every capability. The provider is named on the installation that uses it; your country decides which identity and signing services an installation can offer.
Signing9
Available
Generic CSC 2.0 · Cloud Signature Consortium
Signing
Remote service of a provider
Signing · CSC
Platform key (P12 or HSM)
Signing
Software on the signer’s computer 2 connectors
Signing · PKCS#11
Other · custom PKCS#11 or Minidriver
Signing
Other · REST or direct HSM
Signing
Remote service of a provider
Signing · CSC
Identity14
Identity service
Identity · Provider API
OpenID Connect · generic
Identity
Sign-in with a work directory (OpenID Connect)
Identity
Email and password
Identity
One-time code by email
Identity
Wallet verifier (OpenID4VP)
Identity
One-time code by SMS
Identity
Identity service
Identity
Software on the signer’s computer
Identity · Local bridge
Identity service 5 connectors
Identity
Timestamp1
Time-stamp authority · RFC 3161 over HTTP
Timestamp
Validation4
Remote service of a provider
Validation · Provider API
Own validation engine
Validation
Service of the installation 2 connectors
Validation
Certificate management1
Remote service of a provider
Certificate management · Provider API
Preservation2
Own long-term preservation (B-LTA)
Preservation
Preservation service · ETSI TS 119 512
Preservation
Trust lists3
Own trust anchors
Trust lists
Uruguay trusted list
Trust lists
Remote service of a provider
Trust lists · Provider API
Storage2
Local disk of this server
Storage
Service of the installation
Storage
Events and SIEM2
Service of the installation
Events and SIEM
HTTP collector · security and activity events
Events and SIEM
Email1
SMTP mail server
Messages1
Service of the installation
Messages
Payments2
Service of the installation
Payments
Service of the installation
Payments
Conversion1
Service of the installation
Conversion
Available connectors are part of this release; each installation chooses which ones to switch on. On request connectors have their adapter built and are switched on once the installation has the provider and its configuration. In roadmap connectors are described in the catalogue, with their protocol and the level they enable; their adapter is not part of this release. Connectors to the remote services of trust service providers are listed by what they do; the provider is named only in the operator console, where it is chosen and installed.
Other ways to connect
The API, the signed notices and the other doors, with the same states.
Available
A documented API, with a credential for each integration.
A REST API described by an OpenAPI file, with tokens limited to what each integration needs.
Available
Retry without creating duplicates.
Send an Idempotency-Key on calls that cannot be undone, and a retry with the same key returns the first answer without doing it twice. Answers are kept for 24 hours.
Available
Your systems learn about every event, with a signature and retries.
Approved, signed, rejected, completed and the rest, each signed so you can trust it, with a delivery log. After eight failures in a row the endpoint pauses and the people who can resume it are told.
Available
The document is assembled inside your own network.
A small agent paired to your company puts the document together there: the file and the signed PDF stay with you, and only the proof travels to the cloud.
On request
Your organization’s security events, sent to your own monitoring tool.
Sign-ins, policy and role changes, API tokens and every step of a document, in real time, to Elastic or to any secure web address. Only your organization’s events, with people as pseudonyms and never a document.
In roadmap
Signing inside your own application, without sending people elsewhere.
This is planned: the signing screen would be embedded in your application with a short-lived token, so the signer would never leave it.
In roadmap
Dropping a PDF in a folder to send it out to sign.
This is planned: a watched folder would send what you drop into it, and return the sealed result to the same place.
In roadmap
Connecting your document manager to keep everything in one place.
This is planned: connectors for SharePoint, Google Drive, OneDrive and Salesforce would send documents out to sign and file the signed result back.
On request
Connecting Signing Flows with your systems without writing code.
A flow of steps would send a document to sign, file what was signed or warn your team. Today it is shown in a guided demo, on request.