Certification authorities
Create, import and operate the authorities that establish your PKI's trust.
A certification authority (CA) binds identities to public keys through signed certificates. In Lamassu you can create a new hierarchy, use a key already in the KMS or incorporate an external CA.
To design a full chain or replace an authority in production, see CA hierarchy and rotation. If you need to standardize what each authority can sign, use Certificate profiles.
To administer CAs, you need authority and key permissions, a reachable engine and a reviewed profile. An external consumer does not trust a CA merely because it appears in this inventory: agree root and chain distribution separately.
Choose a flow
- New CA with a new key: create a root of trust from scratch. Lamassu generates and keeps the key pair.
- New CA from the KMS: reuse a key already registered in the platform.
- Import a CA with its private key: incorporate an external authority that Lamassu can issue with.
- Import only the certificate: register public material. If Lamassu finds its key in the KMS, it can associate it; otherwise, the CA has no usable key for issuance.
First time here? Follow Create your first CA to complete the minimal journey.
Create a new authority
Before you begin
- Decide whether the CA will be a root or an intermediate.
- Choose the engine that will keep the key.
- Define a validity longer than that of the certificates it will issue.
- For an intermediate CA, make sure the parent CA is active.
Open the wizard
In Certification Authorities, select Create New CA and choose to generate a new key pair.
Configure the key
Select the cryptographic engine, the algorithm and the size or curve. Lamassu supports RSA and EC keys according to the engine's capabilities.
Use only sizes and curves supported by the engine and the profile’s cryptographic policy. Read Keys and engines before reusing external material.
Choose the CA type
Select Root CA for a self-signed authority or Intermediate CA for an authority signed by another CA. In the latter case, choose the issuing CA.
Define the identity
Enter a unique CA Name. This name becomes the certificate's Common Name. Complete the Distinguished Name fields your policy requires:
C: two-letter ISO 3166-1 country code.ST: state or province.L: locality.O: organization.OU: organizational unit.
The CA's internal identifier is generated automatically and cannot be changed.
Configure validity and uses
Define CA Certificate Expiration and Default End-Entity Certificate Issuance Expiration. You can express a duration (5y 8w 4d), pick a date or use the maximum allowed date.
Review the CA’s own certificate separately from the default profile for certificates it will issue later. Choose an explicit issuance policy; do not assume the form’s initial values suit your consumers.
Create and verify
Confirm the form and open the CA. Check status, issuer, dates, associated engine and key. Download the certificate: it should contain CA:TRUE and a usage permitting certificate signing. Verify the self-signature for a root or the chain to your root for an intermediate. Complete a test issuance to check that the key can actually sign.
Plan validity as a hierarchy
Plan and verify expiration using the Profiles rules. Issuance does not automatically clamp validity to the issuer’s expiration; leave time to replace the authority and renew identities.
Use a key from the KMS
Select Create New CA (Existing Key) when the key is already registered in Lamassu. The wizard first asks for the backing key and then shows the same configuration of type, identity, validity and profile.
This flow is useful when the key was previously created in an HSM, imported through BYOK or must be reused under a specific custody policy.
Import an external CA
You need the CA certificate in PEM, its chain to a known root and, when importing it, an exportable private key. Before uploading material, verify signature, dates, CA:TRUE, signing usages (including cRLSign, without which the CA cannot publish its CRL) and public-key correspondence. The key verification procedure also compares a CA key and certificate.
The backend rejects an import whose certificate lacks the CA basic constraint (basicConstraints cA flag is not set), whose serial number matches a stored certificate with different contents, or whose identical certificate already belongs to an existing CA. A deleted CA's certificate record is kept and can be reused when re-importing the same certificate, including its previous status. Re-importing a different certificate with that serial number is rejected; check the certificate and status after re-importing.
Deleting a CA releases the key references of its own current certificate and linked reissued certificates, while keeping those records for its issuer's CRL and OCSP. It then attempts to delete the key; the KMS keeps it if other certificates still reference it, such as another CA sharing the key. Revoking certificates issued by the deleted CA does not release their own key references.
Select the engine
Check the installation’s default engine before importing a CA with a key. CA import delegates key import to that engine; it does not guarantee arbitrary provider selection from the form. To select an engine while importing the key separately, use the KMS.
Load the material
Import the certificate and, when applicable, its PEM key. Register the CAs needed to identify the issuer. Registering a CA does not install it in external trust stores.
The backend validates before importing any key: a duplicate CA ID and a certificate that is not a CA (missing basicConstraints cA=TRUE) are rejected, the latter with 400 certificate is not a CA: basicConstraints cA flag is not set. If a failure occurs after the key was imported, the key is kept in the KMS and a warning tells you to delete it manually.
Define the default issuance
Associate an explicit issuance profile if the CA will sign. Check usages and dates using Profiles.
Verify the import
Review the registered type, associated key and engine, and issuer relationship. Certificate-only import may associate an existing KMS key using the certificate’s key identifier. Without a usable key, the CA is public material and cannot sign.
For an issuing CA, complete a test issuance and check OCSP and CRL. Creating the record alone does not establish key availability, complete chain consistency or status publication.
Inspect an authority
Open a CA from the inventory to review:
- Status and validity period.
- Certificate and chain in PEM format.
- Number of active, expired and revoked certificates.
- Certificates issued in Issued Certificates.
- The CRL linked to the authority.
- Metadata and the associated cryptographic engine.
You can filter the inventory by name, status and CA type.
Issue certificates
You can start an issuance from Issued Certificates, from a CA's action menu or from the global certificate inventory.
Generate Key & CSR in Browser is useful for a manual operation or a quick test. The browser generates the key and you must download it at the end.
Upload Existing CSR is the right option when the key must remain on the target system. Lamassu receives the request but never the private key.
Follow Issue your first certificate for the guided flow. Certificate management explains the inventory, inspection and revocation.
Revoke a CA
Revocation affects the entire dependent chain
Revoking a CA prevents issuance and may interrupt its entire branch. Only CertificateHold allows reactivating the CA itself if it is not expired. Descendant revocation is attempted with CessationOfOperation; reactivating the parent does not restore those descendants. Follow the cascading revocation conditions.
Assess the impact
Identify the certificates, devices and consumers that depend on the CA. Prepare a replacement authority and chain when necessary.
Start the revocation
Open the authority and select Revoke CA. Choose the reason that describes the incident, for example KeyCompromise, CACompromise, Superseded or CessationOfOperation.
Confirm the identity
Type the CA's name exactly to enable Confirm Revocation.
Check the publication
Check REVOKED on the CA and review descendants individually; propagation permits partial failures. Independently verify OCSP and CRL publication and consumer rejection. A revoked record does not guarantee that an existing session closes.
Delete a CA
Permanent deletion is only available with the CA revoked or expired; a CA imported without a key can be deleted in any state. Delete the record only when your retention and audit policy allows it.
The CA’s CRL settings are kept. A deletion is refused with a 409 error while they are still ACTIVE: the VA must first publish the CA’s final CRL, which can take up to about an hour after revocation with the default job schedule, so retry after the final CRL is published. An expired CA is finalized without a final CRL, and a CA on hold (CertificateHold) is refused with a message asking you to revoke it permanently first. The deletion is also refused with a 409 when the CA’s key signs the CRLs of another CA: the error names that CA, so change its CRL signer, or delete or revoke it, before deleting this one. The CA and all its descendants are checked before anything is deleted; nothing changes if any of them cannot be deleted.
After the deletion, the settings are archived and the last CRL keeps being served but is never regenerated; you can remove them once no certificate issued by the CA still needs revocation evidence, using DELETE /v1/crl-settings/{ca-id} or the console's Verification Authorities page. Deleting them stops the CRL from being served and cannot be undone. Adjust the validity and signer before revoking or deleting the CA (see CRL). The CA’s key is released, but the KMS keeps it while other certificates still reference it.
Lamassu keeps the certificate record of a deleted CA. If that same certificate is imported again, the import succeeds and reuses the record: it updates the type, issuer and key but keeps the status, so the CA reappears in the state it had when deleted (normally revoked or expired). A different certificate with the same serial number is rejected with a 400 error, and a certificate that already belongs to an existing CA with a 409 error. To avoid inheriting the previous status, use a certificate with a different serial number and check the result after importing. The reimported CA is registered under a new, backend-generated CA ID and does not inherit the CRL settings of the deleted CA: until those settings are deleted, those keep serving their last CRL at the CA ID URL, and at /crl/<ski> — the URL that certificates issued before the 4.0.0 upgrade carry — when the settings were migrated by that upgrade; when they are archived, they can no longer be edited (see CRL).