Authorization Instruction

Note：

1. Functions related to authorization must be called before any other SDK function. When they are not called or the call fails, the handle cannot be successfully created.

2. The activation code is recommended to be kept locally, and to be passed in through stid_face_professional_load_license_content interface for authorization verification. By doing so, because the activation code is saved locally, the program does not need to be connected to the network to obtain the activation code.

3. In a software operating cycle, you only need to successfully call the authorization activation interface once. Do not call the authorization activation interface repeatedly, otherwise repeated activation errors will occur.

4. After successfully activating the authorization, do not change key hardware information of the device hardware, including main components such as CPU and all network cards. Note that reinstalling system on some machines could cause the change of device hardware information. Reinstalling system after activation is not recommended on such machines.

5. The online activation authorization method could be used to obtain activation code multiple times. When the device hardware is unchanged, the number of activations will not be consumed. If the device hardware information/hardware changes, an error will be reported during the authentication activation process such as invalid activation code or activation failure. In order to prevent the situation that a device is changed without known, we recommend to back up the activation code after obtaining online, and use the activation code saved on the local or backup server each time for verification.

Authorization activation method：

The Face Verification SDK supports three device binding ways: hardware binding, package name binding and chip binding.

Device hardware binding (online activation license)

Online activation version license activation process (can re-write according to actual business needs during development process)：

Windows/Linux/Arm_Linux:

1. From stid_face_professional_online_activate_license interface, input license file content provided.

2. stid_face_professional_online_activate_license interface automatically sends network request to activation server.

3. stid_face_professional_online_activate_license interface outputs the contents of the newly activated file.

4. From stid_face_professional_load_license_content interface, input the contents of the newly activated file generated by stid_face_professional_online_activate_license.

5. stid_face_professional_load_license_content returns STID_OK, authorization activated successfully.

6. stid_license_release_content releases the contents of the activated license, end of process.

Android:

Online activation version license activation process（can re-write according to actual business needs during development process)：

1. From Class License onlineActivate interface, input license file content provided.

2. Class License onlineActivate interface automatically sends network request to activation server.

3. Class License onlineActivate interface outputs the contents of the newly activated file.

4. From Class License load interface, input the contents of the newly activated file generated by onlineActivate.

5. Class License load interface returns OK, authorization activated successfully.

For the example code of the above calling process, please refer to Sample attached to the SDK.

Package name binding (package name binding version License）

Package name binding license activation process (can re-write according to actual business needs during development process):

Android:

1. Check the consistency of the package name bound to the project and the package name of the delivered license.

2. Under Class License, from the load interface, input the contents of the package name binding version license provided, return OK, authorization activated successfully, end of process.

Chip binding (chip authorization version license)

Chip authorization version License has two sub-versions: chip authorization online license and chip authorization offline license.

Chip authorization online license activation process (can re-write according to actual business needs during development process):

1. Solder the authorization chip provided on the device development board. For chip related instructions and drivers, please refer to the document delivered together with the chip.

2. Refer to online activation section [Device hardware binding (online activation license)](#device-hardware-binding-(online-activation-license) for further instruction.

Chip authorization offline license activation process (can re-write according to actual business needs during development process):

Windows/Linux/Arm_Linux

1. Solder the authorization chip provided on the device development board. For chip related instructions and drivers, please refer to the document delivered together with the chip.

2. From stid_face_professional_load_license_content interfere, input the contents of the chip authorization offline license provided, return STID_OK, authorization activated successfully, end of process.

Android

1. Solder the authorization chip provided on the device development board. For chip related instructions and drivers, please refer to the document delivered together with the chip.

2. Under Class License, from the load interface, input the contents of the chip authorization offline license provided, return STID_OK, authorization activated successfully, end of process.