Device certificate renewal replaces a device’s X.509 certificate with a new one before the old one expires, so the device keeps logging in without a password. The device sends a certificate signing request, receives the new certificate and switches to it. If renewal never happens, the expired certificate is refused at the next connection.
The first certificate is the part people plan for. The lifecycle is what fails later, because a gateway at a remote pump station has to replace its own certificate with nobody on site. Why certificates beat shared passwords is in my post on X.509 client certificate authentication; here I use the defaults of Hermetry’s device certificate authority (CA), whose certificate screens came with release 2.2.2.
How does a device get its certificate?
The device makes its own key pair and asks a CA to sign the public half, so the private key never leaves the device. The request is a certificate signing request (CSR), defined in RFC 2986: a name and a public key, signed with the device’s private key.
In Hermetry, a licensed device sends its CSR over v1/csr and gets its certificate on v1/cert, with the device serial as common name (CN). At every login Hermetry checks the chain, revocation and expiry, and that CN, serial and client ID are equal; there is no fallback to a password. Third-party devices log in with an access token or an MQTT username and password instead, as the device credentials page explains.
How long should a device certificate be valid?
Long enough that renewal stays routine, short enough that a copied key stops working within months. RFC 5280 defines validity as the period from notBefore through notAfter, inclusive, and it allows a device certificate that never expires (notAfter 99991231235959Z) when it binds a model and serial to a key for the device’s whole life.
| Item | Hermetry default |
|---|---|
| Device certificate lifetime | 365 days, settable from 30 to 825 days on the device profile |
| Renewal by the device | Starts at the latest 30 days before expiry |
| Expiry warning to administrators | 30 days, settable from 30 to 180 |
| Key type | ECDSA P-256 for current licensed devices |
I would keep the 365-day default unless a site has a reason to change it. A shorter lifetime means more renewals over patchy links; a longer one keeps a stolen key useful for longer.
What happens when a device certificate expires?
The device is refused at its next login. In Hermetry that refusal is MQTT CONNACK 5, and the fix is to let the device renew or to recover it.
A device whose certificate expired, was revoked or was lost goes through recovery: it provisions again and asks for a new certificate. Check the device clock first, because a clock far off makes a valid certificate look invalid in the TLS handshake, a cause the connection troubleshooting page lists.
Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Devices > ⋯ > Certificates lists every device certificate in the organisation with its status (Active, Superseded, Revoked or Expired) and the days left. Administrators are told about certificates that expire within the Expiry warning and have not been renewed, and Renew certificate asks a device to renew early; it keeps the current certificate until the new one is in use. The device certificates documentation has every setting.
Why would a device ask for a new certificate early?
Because someone reset or repaired it, or because it is a copy. While the current certificate is still valid, Hermetry does not issue a new one automatically:
- You get the notice “A device asks for a new certificate”.
- On the device page, check the key shown with the request.
- Approve revokes the current certificate at once and lets the device obtain a new one for that key within 7 days.
- Reject keeps the current certificate and issues nothing.
Approve only if your team reset or repaired the device. Recovery requests and approvals go to the audit log.
Frequently asked questions
Should a device make a new key when it renews its certificate?
I prefer a fresh key at renewal, so a key that may have been copied retires with its certificate. Hermetry takes that line where the platform generated a certificate’s key and handed it over once: it advises renewing so the device makes a key of its own.
Can I upload my own CA for third-party devices in Hermetry?
No. Uploading your own certificate authority for third-party X.509 devices is not available. Those devices log in with an access token or an MQTT username and password, and the device profile’s Allowed authentication setting decides which types it accepts.
Where do the certificate keys live in Hermetry?
Device private keys stay on the devices. The root keys of the CA are kept offline, the online signing keys are held by one isolated process, and Hermetry never shows or exports a CA private key.

