Skip to content
ConceptForOperatorWith or without Foxden Admin

Running Corsac ​

This page covers what is specific to running Corsac, the e-signature app, on your server: its sealed documents, the secret that protects them, its email and its timestamps.

Where it runs ​

Folder/opt/corsac
Addresssign.<your-domain>
On the server127.0.0.1:3400
Servicesapp, worker, db, migrate, updater
SettingsCorsac settings

Its health address, /api/healthz, answers with an error (503) until the database answers and Corsac's seal certificate exists, so a fresh install is reported healthy only once it can seal.

Its data ​

  • Database: everything about each document, and the names of its stored files.
  • Files: every sealed version of each document, every signature image and the certificates. The database holds only their names, so a database without the files is a list of evidence whose files are gone. Corsac keeps them in its data folder (corsac-data). On a server with Library, the files Corsac stores once it is linked to Library are kept in Library instead.

The nightly backup at 01:25 holds the database and the data folder; Library's backup holds the files kept in Library. See Back up and restore.

The secret that must not change ​

Corsac's APP_SECRET protects the private key of its seal certificate. With a different APP_SECRET, the key cannot be opened, and documents already sealed can no longer be re-signed. It cannot be changed on its own and cannot be recovered. Keep a copy off the server, and on a new server put it back before you restore Corsac. A restore makes no new secrets for Corsac except the ones that tie it to its own server.

Email ​

Corsac sends no email until the server's email is set up: each signing request shows Not emailed, and you send its link to the signer yourself. Setting up email on Server › Connections, or with foxden email set, switches it on. Corsac can also send through your own mail server. See Set up outgoing email.

To see whether each email was delivered or bounced, register Corsac's address https://sign.<your-domain>/api/hooks/email as a webhook in your Resend dashboard, and set the signing secret Resend gives you: printf '%s' '<secret>' | foxden config set RESEND_WEBHOOK_SECRET --stdin --product corsac, then restart Corsac. Without it, Corsac keeps working, but an email's outcome stays pending and bounces are not caught.

Timestamps ​

Corsac anchors each seal with a trusted timestamp from an outside timestamp authority. This is on by default. If an authority is down or not to be trusted, set TSA_ENABLED to false and restart Corsac: sealing carries on without the timestamp. TSA_SPKI_PINS pins the authorities' keys; blank leaves them unpinned.

The trust page ​

Corsac has a public trust page. HOSTING_PROVIDER names the company that hosts your server on it; leave it blank for your own hardware.

Sign-in and people ​

With Admin on the server, people sign in to Corsac through Admin. On its own, the hand-over screen prints a setup link (/setup?token=...) that creates Corsac's first account; foxden console link --product corsac prints it again until that account exists.

Fennec sends documents to Corsac for signature, and Corsac sends signing events back to Fennec. Corsac files signed documents to Library. The installer wires each link that has both apps on the server.

Foxden is open source under Apache-2.0.