As well as using the Registration Tool to install the private key and certificate files, it is possible to manually install them, as described in the following sections.
Installing Key/Certificate in Windows
The private key and certificate files described in Registration Basics can be installed through the Registration Tool, or manually copied to C:\ProgramData\SquareOne\IqEdge
Following installation of the certificates, reboot the device (or restart the service SquareOne Edge Client Service, e.g. via the Windows Services application).
The files will be moved to the C:\ProgramData\SquareOne\Provisioning folder on the next registration attempt, and the device should register and appear in SquareOne Companion. The Provisioning folder on the hidden partition will be used by preference if this exists.
Note that if the device uses a batch certificate it will show as Pending until approved, described below.
Installing Key/Certificate in Linux
The private key and certificate files described in Registration Basics can be installed through the Registration Tool, or manually copied to /var/lib/datav
Their ownership and group should be set to datav:
sudo chown datav:datav device_private_key.pem
sudo chown datav:datav device_cert.pem
Following this, the client component of the SquareOne Agent must be restarted:
sudo systemctl restart dv-edge
The files will be moved to the /var/lib/datav/provisioning folder on the next registration attempt, and the device should register and appear in SquareOne Companion.
Note that if the device uses a batch certificate it will show as Pending until approved, described below.
Installing Key/Certificate in Android
The private key and certificate files described in Registration Basics can currently be installed only through the Registration Tool.
Device Approval
When using a batch certificate, devices require an additional approval stage in SquareOne Companion before the device will complete the registration process. This can be achieved by going to the Management tab of the device page representing the device to be approved.
This process can later be automated or guided based on information passed during registration time.
Single use certificates do not require this approval step.