Supported platforms and scope
Supported Signing Server 1.0.0 platforms, signing profiles, database engines and operational limits.
Signing Server 1.0.0 supports the platforms, signing profiles and database engines listed on this page. Select the installation profile and service mode that match your integration.
Runtime and distributions
Section titled “Runtime and distributions”| Area | Scope |
|---|---|
| Runtime | Java 25. The container and installers include their runtime. |
| Container | Linux x86_64 with Docker and Docker Compose. |
| Installer | Linux x86_64/systemd and Windows x86_64/service manager. |
| Listener | Direct HTTPS with supplied TLS identity, or a private IPv4 listener behind a TLS-terminating proxy. No URL path prefix. |
Service modes and signing profiles
Section titled “Service modes and signing profiles”| Interface | Functional scope |
|---|---|
| DSS human signing | Sweden Connect implementation profile 1.7, DSS extension 1.6 and the documented XML/PDF/detached CMS subset. |
| Exact UTF-8 text | A detached CMS consumer profile over the exact retained text bytes; no separate server upload endpoint. |
| PAdES | PDF/BES with the exact processing rule, preknown actual leaf and consumer B-B/B-T/B-LT/B-LTA assembly, evidence and renewal. |
| XAdES | Detached XAdES XML/BES signing with the exact rule and immutable certificate-bound object, followed by consumer B-B/B-T/B-LT/B-LTA assembly and renewal. Preknown static actual leaf required; no dynamic fresh certificate support. |
| JAdES | Detached JAdES B-B/B-T/B-LT/B-LTA with explicitly enabled local DSS root profile, ObjectIdByURIHash and RS256. Preknown static signing leaf required; consumer-owned encoded evidence and archival renewal with complete CRLs and offline validation. |
| CSC | CSC API 2.2.0.0 subset under /csc/v2, selected by service="csc-v1": discovery, credential information, OAuth PAR/code/S256 PKCE, separate consent, signHash and token revocation. |
| Organization seal | An authenticated machine requester selects an allowed organization profile; no human identification. |
| Time stamping | RFC 3161 with RFC 5816 ESSCertIDv2/SHA-256 certificate binding, using the configured external authority; no human identification or local timestamp issuance. |
| External PKI | Optional SCEP, EST or REST provisioning/activation and supported dynamic person-certificate profiles. REST request and response data are explicitly mapped. |
Signature formats, CSC signing and External PKI and certificate issuance define the selections and limits. Configure the protocol profile and certificate trust described by each integration guide.
Persistence
Section titled “Persistence”| Engine | Scope |
|---|---|
| PostgreSQL | 17 and 18. Distinct migration/runtime accounts are required for CSC and dynamic issuance. |
| MariaDB | 12.3, with separate migration/runtime accounts. |
| Microsoft SQL Server | SQL Server 2025 (17.0), compatibility level 170, with separate migration/runtime accounts and the documented database profile. |
MySQL and Azure SQL are outside the selected adapters. See Databases for exact preparation and privilege rules.
Keys and certificate lifecycles
Section titled “Keys and certificate lifecycles”Supplied keys use PKCS#12 or a pinned PKCS#11 module. The Linux PKCS#11 installation profiles use SoftHSM 2.7. Configure the module, token and key pins as described in Key management.
Optional external PKI supports explicit staging/activation or dynamic human signing. Dynamic signing creates a new key and certificate per transaction after verified identification, with no cross-transaction reuse. Supplied static credentials remain available without enrollment. The runtime never silently replaces an unavailable key or changes backend. Key management describes each lifecycle.
CSC installation profiles
Section titled “CSC installation profiles”| Distribution | Operating system | Crypto | Database |
|---|---|---|---|
| Docker | Linux AMD64 | SoftHSM 2.7 | PostgreSQL 18.6 |
| install4j service installer | Linux AMD64/systemd | SoftHSM 2.7 | PostgreSQL 18.6 |
| install4j service installer | Windows AMD64/LocalService | Supplied PKCS#12 | PostgreSQL 17.11 |
CSC uses fresh SAML authentication, separate browser approval and one-use signing authority in each installation profile. Linux profiles use the configured PKCS#11 token; the Windows profile uses PKCS#12.
Input and response limits
Section titled “Input and response limits”| Profile | Boundary |
|---|---|
| Standard DSS tasks | 1–8 tasks, up to 8,192 decoded prepared bytes per generic task. |
| Selected XAdES | Separate bounds on prepared SignedInfo and the complete object, plus the whole-envelope bound. |
| Local JAdES | Its own bounded signing-message schema and task collection. |
| DSS signing message | Up to 2,048 UTF-8 bytes, plain text or the supported restricted Markdown subset. |
| CSC signHash | 1–64 raw 32-byte SHA-256 digests; preserve duplicate occurrences and use each endpoint's required Base64 encoding. |
| Synchronous response | 30 seconds for supplied/static human signing, CSC, seal and TSA; 180 seconds for dynamic human signing. Every original identity/issuance/consent/transaction/certificate deadline still applies. |
Operational boundaries
Section titled “Operational boundaries”- Pending browser ceremonies do not resume after restart; consumed signing and replay state remains consumed.
- There is no general signing-result polling, push-result or reset endpoint. Registered issuer reconciliation is separate from delivery of a signing result.
- Original documents remain with the requester, which assembles and verifies the finished signatures.
- Installers do not upgrade existing installations or manage operating system accounts. Backup, restore and key rotation use operator-approved procedures.
- Advanced timestamp/LTV augmentation and unlisted signature or CSC profiles are outside the documented scope.