System Requirements

All technical details you may require

System Requirements
(for on-premise use)

Operating Systems

Windows Server 2022

Windows Server 2019

Windows Server 2016

DBMS

Microsoft SQL Server 2019 (Express, Web Edition, Standard or Enterprise)

Microsoft SQL Server 2017 (Express, Web Edition, Standard or Enterprise)

Microsoft SQL Server 2016 (Express, Web Edition, Standard or Enterprise)

Oracle 12c Enterprise Edition

Microsoft Azure SQL Server

SigningHub Enterprise uses Dapper framework so support for other databases can be considered for specific projects – ask for further information.

Additional software components required

IIS 10

IIS 8.5

IIS 8.0

Microsoft .NET Framework v4.8 or above

Go>Sign Desktop app (only required for the local signing use case)

For Windows, download and install it from here Win-32bit, Win-64bit (Run as administrator)

For Mac OS, download and install it from here Mac OS

For installation instructions see Installation Guide

Operator browser

Internet Explorer IE 11

Chrome 40+

Edge 14+

Firefox 35+

Safari 8+ (Local signing is not available for Safari installed on Windows platform)

Opera 26+

Minimum hardware requirements for SigningHub & database server machines

Xeon E56xx or E3 or E5

RAM: 16 GB or above (24 GB recommended)

Microsoft Azure supported (IAAS mode)

200 GB Disk Space

System Requirements
(for on-premise use)

Operating Systems

Windows Server 2022

Windows Server 2019

Windows Server 2016

DBMS

Microsoft SQL Server 2019 (Express, Web Edition, Standard or Enterprise)

Microsoft SQL Server 2017 (Express, Web Edition, Standard or Enterprise)

Microsoft SQL Server 2016 (Express, Web Edition, Standard or Enterprise)

Oracle 12c Enterprise Edition

Microsoft Azure SQL Server

SigningHub Enterprise uses Dapper framework so support for other databases can be considered for specific projects – ask for further information.

Additional software components required

IIS 10

IIS 8.5

IIS 8.0

Microsoft .NET Framework v4.8 or above

Go>Sign Desktop app (only required for the local signing use case)

For Windows, download and install it from here Win-32bit, Win-64bit (Run as administrator)

For Mac OS, download and install it from here Mac OS

For installation instructions see Installation Guide

Operator browser

Internet Explorer IE 11

Chrome 40+

Edge 14+

Firefox 35+

Safari 8+ (Local signing is not available for Safari installed on Windows platform)

Opera 26+

Minimum hardware requirements for SigningHub & database server machines

Xeon E56xx or E3 or E5

RAM: 16 GB or above (24 GB recommended)

Microsoft Azure supported (IAAS mode)

200 GB Disk Space

User devices/Mobile devices

Any operating system with any modern Internet browser supporting HTML5, recent versions of IE 9+, Chrome, Firefox, Safari, or Opera.

For iOS and Android devices the “SigningHub” app is available free of charge, see details.

We also provide a responsive mobile web interface for other mobile devices.

User devices/Mobile devices

Any operating system with any modern Internet browser supporting HTML5, recent versions of IE 9+, Chrome, Firefox, Safari, or Opera.

For iOS and Android devices the “SigningHub” app is available free of charge, see details.

We also provide a responsive mobile web interface for other mobile devices.

Document Formats

PDF, PDF/A and Office 365 Word (2013).

Most document formats can be automatically converted to PDF/A format by SigningHub including DOC, DOCX, XLS, XLSX, PPT, PPTX, ODT, SXW, TXT, RTF, PNG, JPG, GIF, TIF, TIFF, BMP, and EMF.

Long-term digital signatures for Office 365 Word documents are supported using the SigningHub for Word app.

Document Formats

PDF, PDF/A and Office 365 Word (2013).

Most document formats can be automatically converted to PDF/A format by SigningHub including DOC, DOCX, XLS, XLSX, PPT, PPTX, ODT, SXW, TXT, RTF, PNG, JPG, GIF, TIF, TIFF, BMP, and EMF.

Long-term digital signatures for Office 365 Word documents are supported using the SigningHub for Word app.

Private Key Stores

Private signing keys can be stored in a range of devices, i.e.:

For remote (server-side) signing:

PKCS#11 HSMs: Gemalto (SafeNet), Thales or Utimaco (HSMs from other vendors which comply with the PKCS#11 standard should also work)

Cloud HSMs: Microsoft Azure Key Vault HSM, this is a cost-effective cloud-based HSM service which uses FIPS 140-2 Level 2 and Common Criteria EAL4+ compliant HSMs.

For local (client-side) signing:

PKCS#11 smartcards/tokens.

Windows CAPI/CNG key store.

Apple Keychain.

Private Key Stores

Private signing keys can be stored in a range of devices, i.e.:

For remote (server-side) signing:

PKCS#11 HSMs: Gemalto (SafeNet), Thales or Utimaco (HSMs from other vendors which comply with the PKCS#11 standard should also work)

Cloud HSMs: Microsoft Azure Key Vault HSM, this is a cost-effective cloud-based HSM service which uses FIPS 140-2 Level 2 and Common Criteria EAL4+ compliant HSMs.

For local (client-side) signing:

PKCS#11 smartcards/tokens.

Windows CAPI/CNG key store.

Apple Keychain.

Signature Standards

PDF v1.7 (ISO 32000-1:2008) signatures, including certify, approval and long-term signatures.

PDF/A (ISO 19005) signatures.

ETSI PAdES Part 1, Part 2, Part 3 and Part 4 signatures are fully supported.

ETSI XAdES-X-Long signatures as used with Microsoft Office 365 Word and Word 2013/2016 signatures.

Signature Standards

PDF v1.7 (ISO 32000-1:2008) signatures, including certify, approval and long-term signatures.

PDF/A (ISO 19005) signatures.

ETSI PAdES Part 1, Part 2, Part 3 and Part 4 signatures are fully supported.

ETSI XAdES-X-Long signatures as used with Microsoft Office 365 Word and Word 2013/2016 signatures.

User Authentication

Username/password (with optional SMS OTP) across a TLS secured session.

Active Directory Authentication.

Active Directory Federation Services (ADFS) Authentication.

Client TLS certificates.

OAuth and SAMLv2, tested with various external Identity Providers (IDPs) which follow these standards.

Salesforce authentication.

Office 365 authentication.

ConsentID authentication.

Mobile signing solutions (Entrust Identity Guard, Ascertia MSSP Server).

Business applications or portals can also pre-authenticate users and use SigningHub as a seamless, clever “view and sign” feature of the application.

User Authentication

Username/password (with optional SMS OTP) across a TLS secured session.

Active Directory Authentication.

Active Directory Federation Services (ADFS) Authentication.

Client TLS certificates.

OAuth and SAMLv2, tested with various external Identity Providers (IDPs) which follow these standards.

Salesforce authentication.

Office 365 authentication.

ConsentID authentication.

Mobile signing solutions (Entrust Identity Guard, Ascertia MSSP Server).

Business applications or portals can also pre-authenticate users and use SigningHub as a seamless, clever “view and sign” feature of the application.

PKI Standards

X.509 Identity Certificates and Attribute Certificates.

X.509 CRLs (including full, partitioned, indirect & delta CRLs).

RFC 2560 / 6960 OCSP Validation Authorities.

RFC 3161 Time Stamp Authorities are recommended for long-term signatures.

PKI Standards

X.509 Identity Certificates and Attribute Certificates.

X.509 CRLs (including full, partitioned, indirect & delta CRLs).

RFC 2560 / 6960 OCSP Validation Authorities.

RFC 3161 Time Stamp Authorities are recommended for long-term signatures.

Languages

Over 20 common languages are supported including:

English
Nederlands
Español (ES)
Español (LA)
العربية
Français
Deutsch
Türkçe
Latviski
Norsk
Ελληνικά
हिंदी
日本人
Pусский
ไทย
Tiếng Việt
Bahasa Indonesia
Português (PT)
Português (Brasil)
中国
Romana
Srpski

Languages

Over 20 common languages are supported including:

English
Nederlands
Español (ES)
Español (LA)
العربية
Français
Deutsch
Türkçe
Latviski
Norsk
Ελληνικά
हिंदी
日本人
Pусский
ไทย
Tiếng Việt
Bahasa Indonesia
Português (PT)
Português (Brasil)
中国
Romana
Srpski

For in-depth technical details check SigningHub user’s manual