The Signing Certificates page in Signotaur's Admin section (Signing Certs in the sidebar) allows administrators to manage the certificates available to the Signotaur client for code signing and document signing.

A sortable, filterable table lists all registered signing certificates. You can search it by alias, label or subject.
RSA (2048 bits) or ECDSA (256 bits)).For supported certificate types, key algorithms and sources, see Code Signing Certificates and Document Signing Certificates.
The Expires date changes colour as expiry approaches. Hover over it to see the remaining time in words.
| Time to expiry | How it appears |
|---|---|
| More than 21 days | Plain text |
| 21 days or fewer | Amber, with a warning triangle |
| 10 days or fewer | Orange, with a warning triangle |
| 4 days or fewer | Red, with a warning circle |
| Already expired | Struck through and greyed, with a red warning circle |
Expired entries are dimmed in the table. An expired certificate cannot be used for signing and must be renewed or replaced.
A certificate can be registered for code signing, document signing or both. The Purpose column identifies each supported purpose as Code or Doc.
Above the table, Filter by certificate purpose narrows the list to All purposes, Code Signing or Document Signing.
The Purpose column and purpose filter appear only with an Enterprise licence. See Editions & Licensing.
Signotaur determines the purposes from the certificate. A certificate that supports neither code signing nor document signing cannot be registered.
To add a certificate, click Register a certificate. The registration dialog opens for you to enter or select the certificate details.

Signotaur supports four certificate sources, each on its own tab:
Click a heading for instructions on adding that type of certificate.
The Managed tab requires an Enterprise licence. The File, Store, and Hardware tabs are available in every edition. See Editions & Licensing.
Registering and using a document-signing certificate requires an Enterprise licence:
A certificate that supports both purposes can still be registered and used for code signing without an Enterprise licence.
If the Enterprise licence lapses, registered certificates that support only document signing are hidden, not deleted. They reappear automatically when an Enterprise licence is restored, without needing to be registered again.
A registered signing certificate becomes replaced when its underlying managed certificate is renewed and the new certificate takes its place. An amber clock in the Alias column marks the replaced registration. Its tooltip identifies the replacement and, when auto-unregister is enabled, shows when the old registration will be automatically disabled or removed.
To change a certificate's alias or label, click its Edit button.
In the dialog that opens, you can change:

When you edit a certificate's label, the dialog warns you if other certificates use the same label:
Note: Label matching is case-insensitive, so "Production" matches "production".
Labels provide a convenient way to select certificates in the SignotaurTool CLI without updating scripts whenever a certificate is renewed.
Benefits:
--label production instead of updating thumbprints after renewalExample Workflow:
--label productionSee Sign Command - Certificate Selection for CLI usage.
To make a certificate available or unavailable for signing, select or clear its tick box in the Enabled column.
To view a certificate's thumbprint, click the Show Thumbprint button next to its entry. A dialog will open where you can view and copy the thumbprint.
To download a public certificate, click its Download button. The Download Certificate dialog lists the available certificates in the chain and provides PEM and DER downloads for each one.

.cer) for Windows tools and services that require binary certificates. Use Download PEM (.crt) for text-based tools, OpenSSL and Linux trust stores. Both contain the same public certificate..pem) or PKCS#7 (.p7b).For platform-specific guidance on installing a root certificate as a trust anchor, see Trust Distribution.
To assign a certificate to users, click its Assign User Access button.
In the dialog which opens, use the dropdown to select one or more non-admin users to assign the certificate to, then click Save.

Note: Only non-admin users need to be assigned certificates because administrators automatically have access to all certificates.
PKCS#11 certificate passwords can expire. To update a certificate's registered password, click its Update Password button.
In the dialog that opens, enter the password and a password confirmation, then click Save.

Note: Passwords can only be updated for PKCS#11 certificates.
To delete a certificate, click its Delete button, then confirm that you want to remove it permanently.