Production Safety Checklist

A device in the field only connects to the Nabto services if the key information registered in the console matches the private key installed on the device. Most mistakes that affect a production fleet come down to breaking that match or deleting something that is in use. Use this checklist before you make a change in a production organization.

If you are unsure whether an operation is safe, contact Nabto support before you perform it.

General

• The orange organization button shows the organization you intend to change.
• You do not delete devices or products that may be in use. Deleting a product deletes all of its devices and cannot be undone from the console.
• You try out unfamiliar operations in a sandbox organization first.

Nabto Edge

Setting a fingerprint on an existing device in the field disconnects that device. It cannot attach again until either a matching private key is installed on it or its original fingerprint is restored in the console. The console does not warn you when you overwrite an existing fingerprint, neither on the device page nor in a bulk upload.

• A fingerprint upload only contains device IDs from a batch you have just created and that have no fingerprint yet. Never reuse an old file or a file with device IDs from an earlier batch.
• You only change the fingerprint of an existing device when you know the device has a new private key that matches it, for example after a documented key replacement.
• You keep the batch CSV files and fingerprint lists from each production run. They are what you need to restore a fingerprint if one is changed by mistake.

See Edge Provisioning for the recommended process.

Nabto WebRTC

Removing a public key from a device in the field disconnects that device if it uses the matching private key. It cannot connect again until the public key is added back or a new key pair is installed on the device and registered in the console.

• You only remove a device public key when you know the device no longer uses it, for example after a documented key replacement.
• You keep the public keys from each production run. They are what you need to add a key back if one is removed by mistake.
• You only remove a product authorization key when your own backend no longer signs client access tokens with the matching private key. Otherwise clients can no longer reach devices that rely on central authorization.

Uploading device public keys is less risky than uploading Nabto Edge fingerprints: Keys are always added and existing keys are never replaced. Uploading the same file twice does no harm. See WebRTC Provisioning for the recommended process.