Certificates

Certificates (/admin/certificates) manages the trust anchors for signed plugin packages. Active certificates are served to desktop clients at GET /api/certificates/trusted, which the client caches and uses to verify a plugin’s signature before loading it. They are not upstream CA certificates and have nothing to do with the server’s own TLS — that is the reverse proxy’s job (Production deployment).

Adding a certificate

1. Press Add Certificate.

2. Give it a Name you will recognise later — this is the only field you can edit afterwards.

3. Upload the public certificate: .cer, .pem or .crt, up to 10 MB. The thumbprint is read out of the file; an unparseable file is rejected with the reason.

4. Leave Active checked and save.

Revoke flips a certificate out of the served set without deleting it — clients stop trusting anything it signed on their next fetch. Activate puts it back. Delete removes the row outright. None of these touch plugins that were already installed on a client.

Who can manage this

Viewing and managing the certificate list is gated by the Certificates admin area — an Owner, or any admin holding a bundle that grants it. Because a bad or missing certificate can lock every client out of a plugin signed against it, Certificates is one of the three areas flagged high trust when an Owner hands out a bundle.