Issues a new Things5 CA certificate for an existing device (see Device create) and returns it as an archive. Use it with the v2.mqtt.things5.digital broker: the client ID is the certificate id, the UUID prefix of the file names. See Connecting a device.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The archive (zip by default, or tar / tar.gz with format) contains {certificate_id}.certificate.pem, {certificate_id}.private.pem, {certificate_id}.ca.pem and {certificate_id}.public.pem (empty).
The device is unbound from any certificate it had before. Things5 does not keep the private key: store it on the device and do not copy it elsewhere, see Secure device provisioning.
Requires the generate certificates permission on the device. An API integration (client_credentials token) gets 403 if the device is connected: it already has a working certificate. Disconnect it first, or provision it with a pairing code.