Signing methods

SigningHub supports the following signing methods:

Signing methods for web browsers

Server-side Signing - Crypto keys required for digital signature creation are held securely on the server, and only released for signing after user authentication (single or 2-factor authentication). Any modern web browser can be used for signing.
Client-side (Local) Signing - Crypto keys required for digital signature creation are held locally by the signatory, e.g. on secure smartcard/ USB tokens or encrypted software files. In this mode, the signatory's browser requires an up-to-date Java Runtime Environment (JRE).

Server-side Signing - Crypto keys required for digital signature creation are held securely on the server, and only released for signing after user authentication (single or 2-factor authentication). Any modern device can be used for signing.

Last updated 6 months ago

Was this helpful?

SigningHub supports the following signing methods:

Server-side Signing - Crypto keys required for digital signature creation are held securely on the server, and only released for signing after user authentication (single or 2-factor authentication). Any modern web browser can be used for signing.
Client-side (Local) Signing - Crypto keys required for digital signature creation are held locally by the signatory, e.g. on secure smartcard/ USB tokens or encrypted software files. In this mode, the signatory's browser requires an up-to-date Java Runtime Environment (JRE).

Server-side Signing - Crypto keys required for digital signature creation are held securely on the server, and only released for signing after user authentication (single or 2-factor authentication). Any modern device can be used for signing.

Last updated 6 months ago

Was this helpful?