Skip to content

Overview

The Keyserver has three user types. Choose the path that matches your role:


How the Keyserver Works

Typical workflows

Firmware signing

  1. The CI pipeline authenticates using OAuth2 or OIDC.
  2. It creates an operation for a specific signing key.
  3. Approvers, if the key requires them, approve the operation.
  4. The CI pipeline submits a sign order.
  5. The Keyserver returns the signature.

Device certificate issuance

  1. The device generates a key pair and a CSR.
  2. The provisioning tool authenticates.
  3. It creates an operation for the CA key.
  4. Approvers, if the key requires them, approve the operation.
  5. The CSR is submitted to the API under that operation.
  6. The Keyserver signs the certificate with the CA key.
  7. The device receives its certificate chain.

Administrative configuration

  1. An administrator creates a session, and the required number of administrators authorize it.
  2. Roles, subjects, and signing keys are created or updated.
  3. Every change is recorded in the audit log.