GBDS 5 - What's New?
New Features
Fusion (1:1 and 1:N) decision by biometry and mismatch
If micro service and libmultibio returns MISMATCH, exception and group is BIOMETRIC_MISMATCH automatically
If no match is returned by fusion, API and Trust will assume NO HIT
Now group pending can be configured to go to analysis or be directly treated
TRUE
: group treatment can go to pending status, according to user permisisons over all group organizationsFALSE
: group treatment is always final, regardless user permissions over all group organization
A new validation mechanism was introduced for biometric image used in Liveness search to ensure no data was altered during transmission. This mechanism applies exclusively to requests made to the endpoint POST /v2/people/searches with search type set to LIVENESS.
Payloads (specifically the
content
of biometric images) in version 2 are now validated using a cryptographic HMAC signature.
Added verify post match for updates processed on GBDS.
Update fusion rules now apply to enrolls that turned int update
Now "get group" returns a flag indicating if the group is treatable by the user (user has to have the appropriate permissions)
Added new behavior rules
Biometric Target - Documentation
Biographic Target - Documentation
Lights Out Analysis - Documentation
Key Validation - Documentation
Improvements
Start and stop scripts updated
Now delete person endpoint forces memory deletion without having to verify if the person is active and non erased
New version of face quality extraction available
Fixes a problem where flags like busyBackgroundInCropped were being translated to faceLeft
Native libraries libmultbio and matcher multbio updated to 0.3.4, fixing memory overhead problems and crashes
Prioritization now is only available for groups in analysis, pending, refused created or ready to send
Native library Facepad urgraded to 2.3.1, which is used on liveness analysis
Matcher update
New face quality analysis for UPDATE, which now can return face UNCERTAIN
Support for new extractors
Face templates simplification are no longer made on transactions/people
Finger templates are no longer mande on people
Quality control and sequence control are made using multibio comparison
Ginger extractor updated to 2.3.0
Query performance for list groups have been improved
TRUST queries optimizated for:
get next biometric
get next group
count done/remaining groups
Now when a group is refused, it becomes linked to all the exception groups who were responsible for the refusal - more details
Bug Fixes
Fixed bug where update transactions in profiles that were created a long time ago were taking too long
Fixed a bug where Trust was using biometrics from rejected transactions on Enroll Unify treatments
Verify and update 1:1 searches now uses correctly ALL_INDEXES and SAME_INDEX during its execution
Fixed a bug REFUSED status changes were not validating the user permissions
[TRUST] Fixed a bug where refused enrolls were being sent as updates
Fixed a bug where listing people with endDate filter would return error 500
Now if the setting for BoB (Best of Biometrics) use in an update is absent, it is set to true automatically
Fixed a bug where UPDATE exceptions treated with only its reference being kept were getting lost
Now listing people with "include anomalies = false" returns correctly only people not related to an anomaly
Fixed bug where the search result was changing depending on the number of candidates
Fixed a bug where wasn't possible to delete a person when this person was reactivated using a trusted update
Fixed a bug where update transactions received from an update caused by the enroll of a person with non-deduplicated keys were being sent as enroll transactions instead of update
Fixed a bug where update exceptions generated by two profiles with the same face and different fingers couldn't be treated
Fixed a bug where refused transactions were being sent as updates instead of enrolls after reject treatments
Fixed a collateral bug from updates with the same face and different fingers (5.1.12) where it wasn't possible to generate biometric targets nonconformities.
from fusion decision "UNCERTAIN" to target "BIOMETRIC", both enroll and update
from fusion decision "MISMATCH", treted as "NO_HIT", to target "BIOMETRIC", only update, when one modality is "HIT" and the other is "NO_HIT" with no uncertain biometric
Fixed a bug where the forced BoB wasn't working properly for TrustedUpdate transactions on ETR and Print
Fixed a bug where a failure would occur during a refused resend if the template experienced an error during extraction
Verify post match is not performed for enroll anymore, since it could modify the fusion decision
Last updated
Was this helpful?