Overview¶
The Keyserver has three user types. Choose the path that matches your role:
-
Administrator (Part 1)
Sets up and manages the system: signing keys, roles, subjects, and audit.
Start with the Admin Configuration tutorial
Then explore:
-
Developer (Part 2)
Integrates code signing into a build pipeline.
Start with the Sign Code tutorial
Then explore:
-
Provisioning Engineer (Part 3)
Issues identity certificates to devices during manufacturing or onboarding.
Start with the Device Certificate tutorial
Then explore:
How the Keyserver Works¶
Typical workflows¶
Firmware signing
- The CI pipeline authenticates using OAuth2 or OIDC.
- It creates an operation for a specific signing key.
- Approvers, if the key requires them, approve the operation.
- The CI pipeline submits a sign order.
- The Keyserver returns the signature.
Device certificate issuance
- The device generates a key pair and a CSR.
- The provisioning tool authenticates.
- It creates an operation for the CA key.
- Approvers, if the key requires them, approve the operation.
- The CSR is submitted to the API under that operation.
- The Keyserver signs the certificate with the CA key.
- The device receives its certificate chain.
Administrative configuration
- An administrator creates a session, and the required number of administrators authorize it.
- Roles, subjects, and signing keys are created or updated.
- Every change is recorded in the audit log.