Administering a Nabto Solution in the Nabto Cloud Console
The Nabto Cloud Console is where you manage the cloud side of a Nabto Edge or Nabto WebRTC solution: The organizations that own your products, the people and systems that have access, the products themselves and the devices that are allowed to connect to the Nabto services.
Most other guides use the console to set up a single device for evaluation. The guides in this section are for the people who operate a solution day to day, typically in an organization that holds the production configuration for an entire fleet. They explain what each part of the console does and highlight the few operations that can take devices in the field offline.
The screenshots show a fictional company called Acme Lighting. Your console looks the same but with your own organizations, products and devices.
The Nabto Cloud Console is an application built on top of the Nabto Cloud API. Customers can build their own custom integrations as needed, for example with a production line or a support system, using API keys.
Concepts
The console has a small data model. Organizations and users are shared by Nabto Edge and Nabto WebRTC, while products and devices exist separately for each:
| Concept | What it is |
|---|---|
| User | A person with a console login. A user can be a member of several organizations. |
| Organization | Owns products, API keys and a list of member users. Identified by an ID like or-k3h8t2wq. |
| Product | A group of devices, typically one hardware model. Nabto Edge product IDs look like pr-f7x2k9qd and Nabto WebRTC product IDs look like wp-k3mq7rtz. |
| Device | One physical unit. Nabto Edge device IDs look like de-adj2brq4 and Nabto WebRTC device IDs look like wd-hq9xkcmn3tvw4pzj. A device ID is unique within its product. |
| Batch | A set of devices created in one operation. Batches are numbered per product. |
| Fingerprint | Nabto Edge only. A SHA-256 hash of the device’s public key, written as 64 hex characters. A device can only attach if the fingerprint registered in the console matches the private key installed on the device. |
| Device public key | Nabto WebRTC only. A device can have one or more public keys, each identified by a key ID. A device can only connect to the signaling service with a private key matching one of them. |
| Region | Nabto WebRTC only. The region (EU, US or Asia) of the signaling service a product’s devices connect to. |
In both products each device holds a private key that never leaves the device. The console only stores information derived from the corresponding public key. See Nabto Edge Public Key Authentication and Nabto WebRTC Camera Authentication for background.
If you are new to the console, practice in a separate non-production organization first. Every operation described in these guides can be tried there without any risk to real devices.
Guides in this Section
- Logging In and MFA covers access to the console and setting up multi-factor authentication.
- Organizations and Users covers switching organizations, organization settings, members and API keys.
- Edge Products and Devices covers Nabto Edge product settings and how to inspect and edit individual devices.
- Edge Provisioning covers creating Nabto Edge device batches and registering fingerprints for a production run.
- WebRTC Products and Devices covers Nabto WebRTC products, regions, authorization keys and individual devices.
- WebRTC Provisioning covers creating Nabto WebRTC device batches and uploading device public keys for a production run.
- Production Safety Checklist lists what to check before changing anything in a production organization.