2914 views August 11, 2017 November 13, 2020 2

Signing is a part of Signicat’s Signature product. Electronic signing of documents through an integration with Signicat is flexible regarding the choice of signing method, the desired features, as well as the signature process.

The signature process can differ, as the process can be composed to either show the documents(s) first or to require the signer to authenticate first. Both alternatives are described here. Either way, the pending document(s) for signing are presented in the document presenter, a responsive presenter that supports all modern browsers across devices. The signing results is a PAdES, a PDF consisting of all the gathered information through the signature process. More about the signing result can be found here.

Through integration with Signicat, electronic signing of documents can be achieved in two ways; Authentication-based signing or Third-party (or native) signing. Authentication-based signing will be the underlying signing alternative for the signing documentation. Both authentication-based signing and third-party (native) signing are explained in more detail below.

In addition to the signing of documents, Signicat also offers Consent Signature, a headless solution for the signing of text elements such as consent messages. To learn more about Signicat Consent Signature, visit our Consent Signature documentation.

Authentication-based signing

Authentication-based signing is Signicat’s own signing solution. Authentication-based signing supports the use of any type of authentication method provided by Signicat, where the authentication result is used for signing. This ensures a unified output format in accordance with EU specifications, as well as a scalable, responsive signflow supporting all modern device standards and window sizes.

Authentication-based signing enables you to sign one or more digital documents electronically by first consenting to the contents of the document(s) and subsequently authenticating yourself using one of a number of supported methods of authentication, including eID providers.

As the product relies on authentication, the eID providers do not need to support signing themselves. The service gathers proof of the signer’s actions, i.e. viewing the document(s), consenting to the contents, and most importantly the authentication itself. The series of proofs is combined with each of the original documents.

The result – the XAdES (XML Advanced Electronic Signatures) – is digitally signed by Signicat. Each original document results in one XAdES document for each signer. The signed documents can also be merged into a final PAdES (PDF Advanced Electronic Signatures) document using Packaging service.

Third-party (native) signing

Third-party signing, also referred to as native signing, is signing performed by third-party methods and their own, native signing support. Note that this applies only to eID methods that have a signing solution embedded.

Here, the documents to be signed are transferred to the third party provider’s infrastructure. The end-user’s private key is then used to create a digital signature over the original document.

This alternative does not follow the same output formats, cannot be guaranteed to support responsive signflows, and will not necessarily support all of Signicat’s signing functionality.

Third-party (native) signing can be provided with the following methods: Norwegian BankID, Norwegian Buypass ID, Norwegian Commfides, Swedish BankID, Swedish Telia E-legitimation, Danish NemID, Estonian Estonian ID (EstEID), Spanish DNIe and MobileID.


Was this helpful?