|Server Machine(s) – only required when using on-premise||Software: Windows 2008 and 2012 Server (32-bit and 64-bit) with SQL Server 2008 & 2012 (and Express). Also require Microsoft IIS Server v7+ and DotNet v4.5.
Hardware: modern CPU (e.g. Xeon E55xx or E56xx) with 4GB RAM minimum, recommended 8GB+ RAM.
|User Machine(s)||Any operating system with any modern Internet browser supporting HTML5, ideally latest versions e.g. IE v10+. When using local signing then the latest Java Runtime Environment (JRE v7+) should also be installed.|
|Document Formats||PDF. Most other office document formats can be automatically converted to secure PDF/A format on the SigningHub Server, e.g. DOC, DOCX, XLS, XLSX, PPT, PPTX, ODT, SXW, TXT, RTF, PNG, JPG, GIF, TIF, TIFF, BMP, EMF etc. Microsoft Word documents can also be processed in their native format using the SigningHub Office app.|
|Mobile Devices||Native SigningHub apps freely available for Apple iOS iPhone and iPad and Android Devices. Windows & Blackberry apps available upon request.|
|Key Stores||User private signing keys can be stored in a range of devices. For local signing: PKCS#11 smartcards/tokens, the Microsoft CAPI/CNG key store and the Apple Keychain. For server-side signing PKCS#11 HSMs from SafeNet, Utimaco & Thales (standards compliant HSMs from other vendors should also work).|
|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 to Part 4 signatures. ETSI XAdES-X-Long signatures as used by Microsoft Office2013 and Office365.|
|User Authentication||SigningHub can work with 3rd party identity provider solutions which follow industry authentication protocols such as SAML, OAuth & Radius. This includes social media identity providers like LinkedIn and Office365 as well as government e-Identity schemes. Additional authentication protocols can be supported upon request.|
|PKI Standards||X.509 Identity Certificates & Attribute Certificates. X.509 CRLs (including full, partitioned, indirect & delta CRLs). Standard protocols for back-end PKI interfaces: OCSP, TSP, CMC, LDAP/S, SCVP, XKMS, OASIS DSS, OASIS DSS-X.|