Interoperability

The following provides an overview of SignServer's capabilities and support, with relevant links to documentation and external standards.

SignServer supports multiple application servers and standard, high-performance databases. For more information on SignServer requirements, see Prerequisites.

Algorithms

SignServer supports* the following algorithm types and key size/curves.

Algorithm	Key Size/curve
RSA	Keys up to and including 8192 bits.
ECDSA	ECDSA key algorithm with named curves.
EdDSA	Pure EdDSA with Edwards25519 or Edwards448
Hash algorithms	Hash algorithms for signatures, SHA-1, SHA-2.
NSA SUITE B	Compliant with NSA SUITE B algorithms and certificates.
ML-DSA	ML-DSA-44 ML-DSA-65 ML-DSA-87
SLH-DSA	SLH-DSA-SHA2-128F SLH-DSA-SHA2-128S SLH-DSA-SHA2-192F SLH-DSA-SHA2-192S SLH-DSA-SHA2-256F SLH-DSA-SHA2-256S SLH-DSA-SHAKE-128F SLH-DSA-SHAKE-128S SLH-DSA-SHAKE-192F SLH-DSA-SHAKE-192S SLH-DSA-SHAKE-256F SLH-DSA-SHAKE-256S

*See individual workers and crypto tokens for information about what they support. For more information, see Signers Algorithm Support.

Signature Formats

Document Signing

SignServer can easily be adapted to customer-specific needs by using plug-ins and supports document signing formats such as the ones listed below.

Format	Documentation
PDF (ISO 32000) PDF document processing, including support for: Visible signatures. Different certification levels. Requesting and embedding timestamp responses. Requesting and embedding CRLs. Requesting and embedding OCSP responses. PDF permissions.	PDF Signer
PAdES (-B, -T, -LT, -LTA) (PDF Advanced Electronic Signatures)	ENTERPRISE AdES Signer
XAdES (–B, -T, -LT, -LTA) (XML Advanced Electronic Signatures)	ENTERPRISE AdES Signer
CAdES (–B, -T, -LT, -LTA) (CMS Advanced Electronic Signatures)	ENTERPRISE AdES Signer
XAdES (XAdES-BES and XAdES-T)	XAdES Signer
XML (XMLdSig)	XML Signer
CMS/PKCS#7 Generic CMS (PKCS#7) signer signs any document or file with support for encapsulated content or detached signatures and client-side hashing.	CMS Signer
CMS signing with support for time-stamping	ENTERPRISE Extended CMS Signer

Code Signing

SignServer supports code signing formats such as the following.

Format	Documentation
Plain signing	Plain Signer
CMS signing	CMS Signer
OpenPGP signing	OpenPGP Signer
Java code signing including JAR signing Android (APK) signing v1	JArchive Signer
CMS signing + time-stamping	ENTERPRISE Extended CMS Signer
OpenPGP signing with client-side hashing	ENTERPRISE Client-Side Hashing
Authenticode signing including: Signing of Windows Executable files Signing of Windows Installer files (.MSI) Signing of PowerShell script files (.ps1) Signing of Catalog files (.cat) Signing of Cabinet files (.cab)	ENTERPRISE MS Authenticode Signer
Microsoft APPX package signing (AppX)	ENTERPRISE Appx Signer
Java code signing with client-side hashing	ENTERPRISE Client-Side Hashing
Android (APK) signing v1, v2 and v3	ENTERPRISE APK Signer
Debian package signing (dpkg-sig)	Debian Dpkg-sig Signer

ePassport

SignServer is used both for MRTD signing and for ICAO CSCA Master list signing.

ePassport	Documentation
Document (MRTD SOD) signing with Logical Data Structure (LDS) version 1.7 and 1.8 support	MRTD SOD Signer
Document (MRTD) signing	(Legacy) MRTD Signer
ICAO CSCA Master list signing	ENTERPRISE Master List Signer
Additional algorithm support Subject to SoW/support agreement including for instance: Java patch with HSM support for ePassport required algorithms such as SHA256withRSAandMGF1 (RSASSA-PSS) SHA224withECDSA Brainpool ECC curves ...

Time-stamping

SignServer can be used as the time stamp unit within a Time Stamp Authority (TSA) to generate digitally signed time stamps and includes monitoring of time synchronization, offering both RFC 3161 and MS Authenticode time-stamps.

Format

External References

Documentation

Basic Time-stamping

RFC 3161, RFC 5816

Time Stamp Signer

Professional Time-stamping including:

Time synchronization monitoring
eIDAS Qualified Electronic Time-stamping extension

RFC 3161, RFC 5816

ETSI EN 319 422

ENTERPRISE

Extended Time Stamp Signer

Supported Hardware Security Modules (HSMs)

The following table lists HSM support for each SignServer deployment option. Integration methods include PKCS #11 standard and REST APIs. SignServer additionally supports software-based keys for lower security requirements or development.

HSM Type	Software stack	Cloud	Software Appliance	Hardware Appliance	Container Set
Network HSMs integrated with REST APIs
Azure Key Vault / MS Managed HSM	✔️	✔️ Doc link			✔️ Doc link
Fortanix Data Security Manager (DSM)	✔️				✔️ Doc link
Securosys Primus HSM and CloudHSM Service			✔️ Doc link
Network HSMs integrated with PKCS#11
AWS CloudHSM	✔️	✔️ Doc link
Bull TrustWay Proteccio	✔️		✔️ Doc link
CloudHSM Service			✔️ Doc link
Entrust nShield Connect/5c	✔️		✔️ Doc link
Securosys Primus			✔️ Doc link
SoftHSMv2	✔️				✔️ Doc link
Thales DPoD	✔️		✔️ Doc link
Thales Luna 7	✔️		✔️ Doc link		✔️ Doc link
Thales USB HSM			✔️ Doc link
Thales TCT	✔️		✔️ Doc link
Utimaco CryptoServer	✔️		✔️ Doc link		✔️ Doc link
Utimaco u.trust Anchor	✔️		✔️ Doc link
Internal Hardware Appliance PCIe HSMs integrated with PKCS#11
Thales Luna PCIe	✔️			✔️ Doc link
Utimaco PCIe	✔️			✔️ Doc link

Integration Interfaces

SignServer provides multiple integration interfaces, such as:

Client HTTP Interface.
Client Web Service (WS) interface and Admin WS Interface.
SignClient Interface and Administration CLI.
Signum Agents

Native Signing Tools

SignServer supports several native signing tools, such as:

codesign
productsign
rpm-sign