Manage Your Devices
Last updated
Last updated
The Libelium Cloud Bridge service shows in this section all your registered sensor nodes. You can manage two different keys in this section.
API Keys are needed to identify the sensor nodes with the user account and the type of license associated to it. A valid API Key is mandatory to establish a communication with the Libelium Cloud Bridge service.
In other words, API Keys are used to authenticate the calls to the Libelium Cloud Bridge service. Sensor nodes need to include a valid API Key in the headers of their HTTPS calls to successfully connect with the Libelium Cloud Bridge service.
The “Personal Access Keys” section shows all the API Keys which are currently active.
API Keys are transparently generated when using the Programming Cloud Service. As soon as an API Key is generated by the Programming Cloud Service, it is stored in the Libelium Cloud Bridge service, being listed in the “Personal Access Keys” section.
The Programming Cloud Service includes the API Key of each node in the binary programs generated. In the case of programming the sensor using Libelium Waspmote IDE, the API Key needs to be copied from this section and then pasted in the source file.
If the Programming Cloud Service is not used for programming the sensor nodes, an API Key is still needed. In this case the user must manually create this API Key. The user has to insert it in the source code written on the Waspmote IDE.
Click the "Create New Key" button to manually create a new API Key. Manually created API Keys are also listed in the "Personal Access Keys" section.
When creating a new API Key, the user must provide a value in the "Name" field. This is a user-friendly name to tag the API Keys of your devices. Avoiding duplicated names is recommended, because this descriptive text may be used later for identifying the API Keys.
A pop-up window will rise showing the generated API Key. The user may copy it now to use in the source code when needed. The API Key may be retreived anytime later.
The API Key that you have just manually created is listed on the "Personal Access Keys" section. You can access to each API Key by pressing the "Show" button.
If you want to delete an API Key, find the API Key that you want to delete in the "Personal Access Key" list and press on the "Delete" button in the same row.
A message to confirm that you want to delete the API Key will be shown. Remember that after deleting the API Key, it will not be possible to recover it again. Once you delete the API Key, the access to the Libelium Cloud Bridge service will be revoked for the devices using that API Key.
If the user wants to encrypt the payload of frames, an encryption key for each node must be created previously. Encryption keys for the payload (AES-256) are needed when the sensor nodes are programmed to send data values to the final cloud services using end-to-end encryption.
These encryption keys are only useful when the user wants to implement an end-to-end security layer in the final cloud service.
Remember that the Libelium Cloud Bridge service already implements an AES-128 encryption. This encryption is done by default by the Programming Cloud Service in a transparent way for the user. If writing code in the IDE, the user can call a simple function. In either of these two ways, frames travel secured from the sensor node to the Libelium Cloud Bridge service.
Click the "Change key" button to edit the encryption key. In the pop-up window shown there is information about the the properties and values of the encryption key of each sensor node. In the top-left of the window the device name and the device serial id are shown, these two values identify the sensor node.
The current value of the AES-256 encryption key of the sensor node is shown in the field "Encryption key (AES 256)", an initial random encryption key is assigned to each node in the activation process of the Services Cloud Manager.
This value will be used by the Programming Cloud Service when choosing the option to encrypt the frames for this sensor node. If writing code in the IDE, the user should copy the value from this field to the source code.
The value of the AES-256 encryption key assigned to the node may be modified: the field "Encryption key (AES 256)" is editable and any text that complies with the AES-256 requirements may be typed, using a custom value or generating a new random AES-256 encryption key.
Click the button "Generate Random Key", next to the editable field, and a new valid AES-256 encryption key value will be presented in the editable field. It is possible to click the button as many times as desired to get different values. Finally, click the button "Save" at the bottom to assign the new value to the sensor node.
AES-256 encryption keys may be edited as well from the “My Devices” section of the Services Cloud Manager, click the pencil icon on the "Action" column to open the edit window and check or modify the current encryption key assigned to each sensor node.
Generate a new random key to overwrite the existing key is also possible.
