Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This page describes how to update to a higher version of SenseID.
In this manual, we will guide you through the update procedure updating SenseID from V1.7.0 to V1.8.0.
As a preparation, unzip and place the V1.8.0 package 1v1-private-cloud-v1.8.tgz
in the same directory where V1.7.0 is installed.
Change the directory to the old version folder, and stop the Ruby-Cloud-API service.
Refer to Section 4.2.1 Adjust CPU cores, Section 4.3.2 Set Go-Workers address, Section 4.3.3 Adjust CPU cores in the Installation Manual, set the number of CPUs and the address of Go-Workers in the new version's configuration file as in the old version.
Change the directory to the new version folder, and load the Ruby-Cloud-API image file.
Start the Ruby-Cloud-API service of the new version.
Change the directory to the old version folder, and stop the Go-Workers service.
Copy the license files from the old version to specified folders of the new version.
After receiving senseid_kestrel.lic
, copy it to the specified folder of the new version with the following command.
Change the directory to the new version folder, and start the Go-Workers service.
Check if services started normally.
Ruby-Cloud-API
Go-Workers
senseid_kestrel.lic
is required since V1.8.0. If you have not received it yet, please contact the JCV product window () with the UDID.txt file and your contract number. For details, refer to Chapter 2 UDID in the Installation Manual.
This manual provides instructions during the operation of SenseID.
This manual describes each operation procedure required for SenseID.
This manual is intended for customers who belong to the IT department and have experience using and operating Linux, Kubernetes, Docker, and cloud.
This page describes the standards of input photos and videos for using the SenseID API.
The photo format should be one of the following. JPG (JPEG) ,BMP, PNG, GIF, TIFF The recommended format is JPG (JPEG).
The width and height of the photo should be at least 32 pixels and no more than 5,000 pixels. The recommended size is 640*480 pixels.
The size of the photo file must be 5MB or less. The larger the size, the more the processing performance will be affected. We recommend compressing the photo file to 100KB.
Most common video formats are supported. Include but not restrict to MP4, AVI, FLV, WMV, MOV, RM
The recommended format is MP4.
The width and height of the video should be at least 8 pixels and no more than 5,000px. The recommended size is 640*480 pixels.
The size of the video file must be 16MB or less. The larger the size, the more the processing performance will be affected. We recommend compressing the video file to about 500KB to 1MB.
This page describes the photo and video encryption method for using the SenseID API.
SenseID requires that personal data (photos and videos) must be encrypted before being uploaded via APIs. AES-256-GCM is adopted as the encryption algorithm. The key and IV required for encryption are set as follows by default.
To customize the key and the IV, update the environment variables PARAM_DECRYPT_KEY
and PARAM_DECRYPT_IV
. The key is 32 characters and the IV is 12 characters.
Load the photo or video file.
Encrypt the data with AES-256-GCM.
Encode the above result with Base64.
This page describes how to change or renew the license of Sense ID.
To change or renew the license files, overwrite the new license files from the old licenses file and place them in the specified directories. Refer to Chapter 3 License Activation in the Installation Manual for details.
After replacing the license files, restart the service.
This page describes the error code that occurs during the operation of SenseID.
Date
Revised content
2021/08/20
The first edition released
error_code
Value
Description
STID_OK
0
Success
STID_E_INVALID_ARG
-1
Invalid parameter, please check whether the value of each input parameter is correct
STID_E_HANDLE
-2
Handle error, please check whether the input handle is correct
STID_E_OUTOFMEMORY
-3
Insufficient memory, system error
STID_E_FAIL
-4
Operation failure, internal error
STID_E_INVALID_PIXEL_FORMAT
-6
The image format is not supported, please refer to the interface description
STID_E_FILE_NOT_FOUND
-7
Resource file not found (such as license, model, etc.). Check whether the input path is correct
STID_E_INVALID_FILE_FORMAT
-8
Incorrect file format, mainly related to the model file
STID_E_MODEL_FILE_EXPIRE
-9
Model file expired
STID_E_INVALID_AUTH
-13
Illegal license file (for example, the product name is not consistent), or license file does not load.
STID_E_AUTH_EXPIRE
-15
license file or SDK expires
STID_E_UDID_MISMATCH
-16
UDID mismatch, and the hardware fingerprint bound to the license is inconsistent with the current device’s hardware fingerprint
STID_E_VERSION_MISMATCH
-23
Product SDK version mismatch. The current SDK version is beyond the version range specified in the license
STID_E_PLATFORM_NOTSUPPORTED
-24
The platform is not supported. The current running SDK platform is inconsistent with the platform scope specified in the license
STID_E_MODEL_UNZIP_FAILED
-25
Model decompression failed, please check whether the model file is damaged
STID_E_SUBMODULE_NOT_FOUND
-26
Submodel does not exist, please check whether the use of the model file is correct
STID_E_CAPABILITY_NOTSUPPORTED
-2067857410
Use an interface that does not support capabilities in the license
STID_E_GET_UDID_FAIL
-2146304001
Failed to get the UDID
STID_E_READ_MODEL_FILE_FAIL
-10
Failed to read the model file
STID_E_LOAD_LIBRARY_FAILED
-2065563655
Failed to load dynamic library
STID_E_ONLINE_ACTIVATE_PARENT_LICENSE_NOT_FOUND
-2145517553
The parent license can't
STID_E_ONLINE_ACTIVATE_PARENT_LICENSE_TOO_MANY
-2145517552
Too many parent certificates of the authorization file, up to 10 levels