Was this content helpful?
How could we make this article more helpful?
A computer installed with Lyve Client used to access assigned Lyve Mobile devices.
An app used to unlock specific Lyve Mobile devices. Lyve Client can be used to access devices using Lyve Portal Identity and/or Lyve Token Security.
Security option that allows an end user to enter a username and password to authorize host computers to access connected Lyve Mobile devices. End users must have a Lyve user account. Internet connectivity is required during sign-in and when periodically reauthorizing a host computer. See Accessing Devices with Lyve Portal Identity.
An encrypted security token file authorizing a host computer to access specific Lyve Mobile devices.
Security option that allows for use cases in which there is limited access to the internet when using Lyve Mobile Arrays. End users are not required to have a Lyve user account. Instead, the end user creates a registration file for the computer in Lyve Client and then sends it to the project administrator. The project administrator uses that registration file to generate a Lyve Token file in Lyve Management Portal and then sends it to the end user. Internet connectivity is required to download the installer for Lyve Client, but is not required when accessing devices with Lyve Token files. See Accessing Devices with Lyve Token Security.
Administrator in the account permitted to:
End user accessing Lyve Mobile storage devices from a connected computer.
A JSON file certifying Lyve Client on a specific host computer.
In Lyve Management Portal, an unlocker has the correct security permissions to unlock one or more Lyve Mobile Arrays. For example, an instance of Lyve Client installed on a host PC. Multiple Lyve Mobile Arrays can be assigned to a single unlocker, or to multiple unlockers.