Skip to content

Fortified IDDocs

Installation

How to install Fortified ID Signing Server with Docker or an installer, and verify that it is ready.

Signing Server is delivered as a container image, as a Linux and Windows installer, and as a common archive that both are built from. All of them run the same server with the same configuration file.

Prepare the infrastructure and protected transport identities before the first start. Document credentials may be supplied, explicitly provisioned or dynamically issued according to the selected mode.

  • A database and accounts for the engine you selected. See supported platforms.
  • The distinct transport identities required by the selected mode. DSS uses TLS, SAML signing/decryption and a DSS response key; CSC has its own SAML roles. Supply a static document credential or configure the optional issued-credential lifecycle.
  • The registered requesters and their public keys and return URIs.
  • The identity provider connection metadata and its SHA-256 pin.
  • Passwords and PINs in owner-protected files, mode 0400 or 0600 on POSIX or equivalent ACLs on Windows. Never put a secret in a command line, in the JSON configuration or in an environment variable.

Keep configuration and keys outside the program directory.

The signing-server launcher, with signing-server.cmd on Windows, provides these commands:

Command Description
--version Prints the product and configuration version.
config-check <file> Validates the configuration syntax offline. It does not open key files or connect to anything, so success does not mean the server can start.
database-check <file> Probes the database with the runtime account without changing it.
start <file> Validates all key material, identity provider configuration and listener topology, runs schema migrations, binds the listener and reports SIGNING_READY.

Exit code 0 means the command succeeded, 2 means invalid usage and 3 means a configuration or startup failure. Diagnostics are fixed codes and never contain input values or paths.

  1. Run config-check against your configuration.
  2. Run database-check to verify the database connection.
  3. Start the server and wait for SIGNING_READY.
  4. Request GET /health/live and GET /health/ready. Readiness checks key material, identity provider metadata validity and database availability without migrating. Both return only UP or DOWN.

In this section