The following table defines the system requirements for SigningHub Enterprise:


SigningHub Enterprise Requirements

Component

Description

Server System

SigningHub Enterprise is a Microsoft .NET Framework application and is supported on these operating systems:

  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016

IIS is a mandatory component. The versions stated below are supported. For more information refer to Prerequisites :

Hardware: A modern multi-core CPU such as the Xeon E56xx or the E3 or E5 range is recommended, with a minimum of 16GB RAM and 200 GB disk space required for the application and its logs. 32GB RAM and higher is needed to support a larger population of concurrent users.

In case you are Using Microsoft Windows 2022 Server and Installing SigningHub. TLS 1.3 is by default ON on Windows Server 2022 (integrated applications should support TLS 1.3). Client Certificate Authentication is not supported with TLS 1.3 and as a workaround disable TLS 1.3 by Enabling the checkbox to Disable TLS 1.3 over TCP in your IIS Bindings.

Database Server

SigningHub Enterprise supports these databases to store the configurations data:

  • Microsoft SQL Server 2019, 2017, 2016 (Express, Web Edition, Standard or Enterprise)
  • Microsoft Azure SQL Server
  • Oracle 19c

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


SigningHub Enterprise database can be installed on the same machine as the SigningHub Enterprise application. However, for optimal performance it is recommended to use a dedicated host, either virtual or physical. 

Hardware: A modern multi-core CPU such as Xeon E3-xxxx or E5-xxxx series is recommended, with a minimum 16GB RAM (24GB RAM recommended). In addition, 30GB of disk space as a minimum for document storage of File System, and 50GB for Database Storage, with the upper level determined by the online storage requirement.

In case you are installing SigningHub using Microsoft SQL Server 2016, upgrade the database instance to latest service pack, which is SP2. To download the SP2 service pack, visit Microsoft's Download Center.

Client Machines 
(systems using the service)

The following client machines/devices are supported:

  • Windows 10, 8, 7 Browser support for central and local signing
  • Linux (any)  Browser support for central and local signing
  • Mac OS X 10+  Browser support for central and local signing
  • iPad (iOS 9+)  SigningHub App supports central signing only
  • iPhone (iOS 9+) SigningHub App supports central signing only
  • Android 5+ SigningHub App supports central signing only

Web Browsers
(for end-users and administrators)

The following browsers are supported:

  • Internet Explorer (IE) 11+ 
  • Edge 14+
  • Firefox 35+
  • Chrome 40+
  • Safari 8+ (Local signing is not available for Safari installed on Windows platform.)
  • Opera 26+


The following table defines the system requirements for ADSS Signing Server:


ADSS Signing Server Requirements

Component

Description

ADSS Signing Server

ADSS Signing Server 6.0.x or above is a mandatory component of the solution.  It provides the underlying security services required by SigningHub Enterprise.

Note that ADSS Signing Server may be installed on the same server platform as SigningHub Enterprise and is silently installed as part of the installation process.  However, a dedicated, separate installation of ADSS Signing Server can also be used. Database requirements for ADSS Signing Server differ to those from SigningHub Enterprise. Please refer to the ADSS Signing Server documentation suite for more information: http://manuals.ascertia.com/ADSS-Admin-Guide 

Regardless of the deployment model chosen, SigningHub Enterprise and ADSS Signing Server must have their own respective databases.

 Compatibility with Versions of ADSS Server

 SigningHub is compatible with ADSS Server versions

  • 8.1.2
  • 7.1
  • 6.9.0.3

 except for the below features that are not supported:

  ADSS Server 6.9.0.3

  • Add "XADES_SIGNATURE_TYPE" key, with value "ES-X-L", to perform a XAdES Extended signature (SHE-32780)

Admin/Operator web browsers

For ADSS Signing Server Admin interface these browsers are supported:

  • Internet Explorer 9+ 
  • Edge 14+
  • Chrome 40+
  • Firefox 35+

Optional HSMs

The following Hardware Security Modules (HSMs) are supported:

  • Thales SafeNet Luna SA, Luna PCI, Luna G5
  • Thales SafeNet Protect Server (PCI or External)
  • nCipher nShield Solo or Connect HSMs
  • Utimaco HSMs
  • Azure Key Vault
  • Amazon AWS Cloud HSM

DMZ Proxy Systems

A DMZ proxy server is recommended to provide enhanced security for SigningHub Enterprise. Supported web servers are:

  • Windows Server + IIS or Apache or IBM HTTP Server
  • Linux + Apache or IBM HTTP Server

Ascertia recommends a reasonable CPU, 4GB RAM, 1 GB disk space for the web server host.
SigningHub Enterprise and ADSS Signing Server support network proxies to allow authenticated access to external services.

Signing with local smartcards or USB Tokens requires ADSS Signing Server Go>Sign Service, which requires IIS Application Request Routing (ARR) module as a proxy server (if used).  See Configuring Application Request Routing for Local Signing for details.


SigningHub Enterprise, ADSS Signing Server, and the database can all be installed on the same system for testing purposes. However for optimal performance and production systems, Ascertia recommends that the database should be installed on a dedicated host. If required ADSS Signing Server can also be installed on a separate server. 

The details given above are the minimum system requirements; these may need to be revised to meet specific performance requirements. SigningHub Enterprise and ADSS Signing Server can also be configured in a load-balanced mode to provide higher resilience and throughput.