Specifications

Checkout the technical specifications
Technical Details
System Requirements (for on-premise use)
  • Operating systems:
    • Microsoft Windows Server 2016 (32 & 64 Bit)
    • Microsoft Windows Server 2012 R2 (32 & 64 Bit)
    • Microsoft Windows Server 2012 (32 & 64 Bit)
  • DBMS:
    • Microsoft SQL Server 2016 (Express, Web Edition, Standard or Enterprise) or
    • Microsoft SQL Server 2014 (Express, Web Edition, Standard or Enterprise), or
    • Microsoft SQL Server 2012 (Express, Web Edition, Standard or Enterprise).
  • Additional software components required:
    • Microsoft IIS 8.0 or above
    • Microsoft .NET v4.0
    • Go>Sign Desktop (for local signing)
    • Microsoft Azure supported (IAAS mode).
  • Operator browsers:
    • Internet Explorer 9 or above
    • Chrome 30 or above
    • FireFox 25 or above
    • Safari 5.1 or above
    • Opera 25 and above
  • Minimum hardware requirements for SigningHub & database server machines:
    • 20 GB Disk Space
    • Xeon E56xx or E3 or E5
    • RAM: 8 GB or above
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 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.
Private Key Stores

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

  • For server-side signing:
    • PKCS#11 HSMs from Amazon, Gemalto (SafeNet), Thales or Utimaco.
    • PKCS#11 compliant HSMs from other vendors should also work.
    • Azure Key Vault HSM – enhancing the protection of user signing keys inside the Azure Key Vault FIPS140-2 Level 2 and CC EAL4+ compliant cloud-based HSM (a more cost-effective solution than providing users with locally held smartcards or secure USB tokens).
  • For local 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 Office 365 Word and Word 2013 signatures.
User Authentication
  • Username/password (with optional SMS OTP) across a TLS/SSL secured session.
  • Active Directory Authentication.
  • Active Directory Federation Services (ADFS) Authentication.
  • Client SSL certificates.
  • OAuth and SAMLv2.
  • 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.
CRM Integrations
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