Auth keys form the permission model of ondevice. You can manage your keys in your control panel
You need to call ondevice login
with one of those keys on each system you want
to use with your ondevice account.
For personal use, a single full
key is probably enough.
For more complex setups, we recommend a single device
key (or one per
group of devices) and distinct client
, full
or custom
keys for each end
user (or maintenance script) working with your devices.
ondevice.io tracks usage stats for each individual key. Using more keys gives you more details on how each of them is being used.
We provide roles that each come with their own set of permissions (for details see the matrix below)
full
: has access to the whole account. Most useful for smaller setups
(e.g. your personal ondevice.io account)client
: read-only access to your account
ondevice list
)ondevice ssh
, ondevice rsync
, …)ondevice device $devId list
)ondevice daemon
device
: can only run ondevice daemon
disabled
: Disables the given auth key.custom
: Allows you to configure each permission individually.Roles | Permissions | |||
---|---|---|---|---|
full |
client |
device |
disabled |
|
device Allows the client to run ondevice daemon
|
||||
connect can run ondevice ssh etc. to connect to your devices
|
||||
get_properties has read access to device permissions |
||||
list_devices can list devices |
||||
set_properties can set/remove device properties |
||||
manage_devices can rename and delete devices |
Note: There’s also the deprecated manager
role which is similar to the new
full
role but lacks the device
permission. This role will be removed soon
and keys using it migrated.