Supported Databases

The following databases are supported in SignServer, based on deployment.

For more information about the available deployments, see Installation.

For information about setting up databases, see Database Setup.

Multiple SignServer Nodes Sharing the Same Database

When nodes share a database, configuration changes made on one node are not automatically applied to other nodes. The changes must be reloaded explicitly on each node.

Worker Configuration (including Authorization Rules)

The Worker Configuration page in Admin Web always displays the latest configuration from the database. Editing a Worker's configuration updates the database, so all other nodes will immediately see the same values on their configuration pages.

However, the displayed configuration may not match the active configuration being used to process signature requests. A loaded worker continues using the configuration from when it was last loaded until a Reload command is issued on that node.

• The currently active configuration is visible on the Worker Status page.

• Admin Web automatically issues a reload on the current node after saving changes. To apply changes to other nodes, use the Reload from Database command on each node through the API, CLI, or by logging into Admin Web on each node and clicking the button.

• CLI/API: Always manually issue the reload command after making changes.

Global Configuration (including Administrator Rules)

Unlike the Worker Configuration page, the Global Configuration and Administrators pages display the active configuration on the current node, not necessarily the latest from the database. Saving a change updates the database and reloads all global configuration properties on the current node.

Because the page may not reflect the latest database values, there is a risk of overwriting more recent changes made on another node. Best practice: always reload from the database before making changes.