Certificate authorities
CID Hub stores the root and intermediate certificate authorities (CAs) that CIDs need to trust corporate server certificates. CID Hub distributes the public certificates to both the CID Linux host and its embedded Windows VM.
Certificate fields
The Certificate Authorities page displays identity, validity, and audit information.
| Field | Meaning |
|---|---|
| Name | The name assigned during import. |
| Subject | The certificate subject's full distinguished name. |
| Issuer | The issuing authority's full distinguished name. A root CA is self-issued. |
| Valid From / Valid To | The certificate validity period. |
| Imported By / Date Imported | Who imported the CA and when. |
| Modified By / Date Modified | Who last changed the CA and when. |
Validation rules
CID Hub accepts X.509 certificates in Privacy-Enhanced Mail (PEM) format. An import can contain a certificate chain, but it must not contain a private key. For CA-issued server certificates, importing the root and intermediate CAs allows the CID to trust certificates issued by that chain. A standalone self-signed server certificate must be imported separately.
Both the Administrator and User roles can view the account's CAs. Administrators can also import, edit, and delete them.
Distribution and lifecycle
A CID synchronizes trusted CAs at boot, at least once every 24 hours, and before an operation that re-registers it with the OpenLab Server. CID Hub distributes certificates but does not renew them. Renewed CAs must be imported and coordinated with certificate replacement on the affected servers and clients before the existing certificates expire.
For procedures, see Use corporate certificates.
Last updated: