Expanded the list of data errors on the Attempts page in the dashboard.
Added the ability to disable unnecessary ingress for modules.
Added the ability to redefine UI logic for rendering a face border and a face mask based on keypoints.
Added the ability to redefine UI logic for Motion Control direction hints.
Update locales for Web-component.
The overlay settings block has been removed from the motionControl and faceBestshotSettings blocks of the component configuration. The background when displaying the face frame is now configured by defining a custom version of the FaceBorder UI element.
Added support for configuring data deletion policies individually for each account.
Face SDK library updated to version 3.28.1.
Updated the frame quality calculation algorithm. You can now view reasons for quality failures in the dashboard and customize which checks should be ignored.
Updated attempt creation logic — an attempt is now initialized at the start of a session and finalized at the end.
Updated the face detector in the web component.
Revised the logic of calculating head rotation angles in the web component.
Removed the following configuration settings from the web component: autoSubmit, obtainReferenceFrame, focalLength.
System Performance Reports: Added the ability to receive detailed reports with system performance metrics.
Liveness calculation results now include information about the detected attack type.
Introduced a new endpoint to get video-recorder service metrics in prometheus format.
Transport for data transfer in the web component has been changed from HTTP to WebSocket.
Flexible Check Configuration: Users can now customize the order of validation checks and disable Motion Control and Liveness Reflection (WebSocket only) in the web component.
Added the ability to overwrite settings received from the server via client-side configuration.
Added an error display in the web component when retrieving component setting fails.
Resolved an issue where sorting by validationRequestId for RiskEvents in publicapi was incorrect.
Fixed an issue where face settings did not affect Motion Control validation in the web component.
Corrected a bug causing "Server Error" to be displayed instead of specific validation errors in the web component.
Fixed a slowdown issue triggered by repeatedly clicking the “Refresh” button in the web component.
Resolved an issue where multiple requests were made to access the camera in Telegram.
Fixed a bug where validation requests were executed before the server processed Liveness Reflection and Motion Control data when "autoSubmit" was enabled.
Fixed a problem causing the web component to hang on mobile devices when the browser session allowed camera access, but application permissions denied it.
A setting for MassAttack risk parameters has been added to the dashboard.
The LRS logic has been split into two separate services. The Video Recorder is responsible for recording and saving attempts with video, while LRS is responsible for calculating liveness from the video.
Display of the applicant's "Reference ID" has been added to the dashboard.
Display of the risk list has been added in response to the "Validation" request.
Descriptions of attempt statuses have been added to the dashboard.
Added a setting to limit the number of simultaneous WebRTC connections.
Added a setting to disable video recording for performance improvement.
Added the ability to record video via HTTP requests.
Added a request to retrieve an applicant by Reference ID.
Added configuration of web components on the server.
The configuration has been updated:
Added the fingerprintWaitTime field.
lrsToken has been replaced with videoRecorderToken.
lrsDecryptKey has been replaced with videoRecorderDecryptionKey.
Added ability to customize storage time of video and reference photos in LRS. The retention period is configured in the minio.data_retention_days variable in values of the LRS service upon deployment.
Added attempt pagination to dashboard and publicapi.