Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Name: CTK 1.4.1
Date: 22nd Nov, 2024
Name: CTK 1.4.0
Date: 15th April, 2024
Name: CTK 1.3.0
Date: 5th January, 2024
Name: CTK 1.2.0
Date: 14th July, 2023
Name: CTK 1.0.0
Date: 19th February, 2023
Name: CTK 1.0.0
Date: 3rd February, 2023
Name: CTK 0.0.9
Date: 1st December, 2022
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices:
The Windows Compliance tool kit was tested with the below specifications:
ABIS (Automated Biometric Identification System) Specifications were tested with Fingerprint, Iris and Face modalities as per MOSIP ABIS API specifications.
Secure Biometric Interface (SBI) with Compliance testcases collection and Quality Assessment testcases collection on below modalities
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
Biometric SDK
Quality Check
Match
Extraction
Conversion
The Android Compliance tool kit app v1.4.0 was tested with the below specifications:
Secure Biometric Interface (SBI) with Compliance testcases collection and Quality Assessment testcases collection on below modalities
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
MOSIP interfaces with an Automated Biometric Identification System (ABIS) to perform de-duplication of a resident's biometric data. A country may use multiple ABISs for the same biometric data and evaluate the best ABIS based on de-duplication quality. ABIS is used for 1:N de-duplication. For 1:1 authentication, Biometric SDK is used. MOSIP does not recommend using an ABIS for 1:1 authentication.
Test cases have been tested with MOSIP mock ABIS for compliance with the MOSIP specifications across 29 test cases.
Out of scope: Real ABIS testing in CTK 1.4.0
The Secure Biometric Interface (SBI) is used to interface with biometric devices. The compliance tool kit was tested to ensure that the interface built by the device provider is following the specs and security rules defined in the SBI spec. The device hardware security features are not tested as part of compliance tool kit.
The ‘Android CTK app v1.4.0’ with ‘MOSIP Android Mock SBI’ has been tested for compliance with the specifications. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI.
The Android CTK app v1.4.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI and real registration face SBI.
The Windows CTK 1.4.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications.
The Windows CTK 1.4.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications.
Out of scope: Real devices testing on Windows and android CTK v1.4.0.
The SDK implementation has been tested to support quality check, match, extraction, and conversion of biometrics. Test cases have been tested with MOSIP mock SDK.
Out of scope: Segmentation testing and Real SDK testing.
mosipqa/compliance-toolkit-batch-job:1.4.0
mosipqa/compliance-toolkit-service:1.4.0
mosipqa/compliance-toolkit-ui:1.4.0
mosipqa/postgres-init:develop
mosipid/config-server:1.1.2
mosipid/kernel-auditmanager-service:1.2.0.1-B1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipqa/authentication-internal-service:release-1.2.0.1
mosipqa/authentication-otp-service:release-1.2.0.1
mosipqa/authentication-service:release-1.2.0.1
mosipid/kernel-keymanager-service:1.2.0.1-B2
mosipqa/keycloak-init:develop
mosipid/partner-management-service:1.2.0.1-B3
mosipqa/partner-onboarder:develop
mosipid/kernel-notification-service:1.2.0.1-B1
Currently, ABIS partners can successfully create SBI and SDK projects in CTK 1.4.0, although role-based constraints to restrict this functionality is planned for future release
Release Name: CTK 1.4.1
Support: Patch Release
Release Date: 22nd Nov, 2024
Modified the collection ID generation logic to ensure unique collection IDs are created for every new project.
Conducted extensive testing to validate the fix and ensure the system's responsiveness and data consistency.
Updated the error handling mechanism in the Dashboard to address issues with projects that encounter errors while fetching their last test run’s status.
Enhanced collection ID generation logic with a unique identifier mechanism.
This hotfix is compatible with the dependencies listed below; no additional updates are required.
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
Post installation, follow the setup steps available here.
Scenarios
Mock ABIS
Total
28
Passed
27
Pending
0
Failed
0
NA
1
Test Rate (%)
100%
Pass Rate (%)
100%
Scenarios
Finger
Iris
Face
Total
35
27
41
Passed
35
27
41
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
90%
100%
Scenarios
Finger
Iris
Face
Total
49
26
45
Passed
49
26
45
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
35
27
41
Passed
35
27
41
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
55
29
48
Passed
55
29
48
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
With Mock SDK
Total
65
Passed
65
Pending
0
Failed
0
Test Rate (%)
100%
Pass Rate (%)
100%
Repositories
Tags Released
mosip-compliance-toolkit
v1.4.1
mosip-compliance-toolkit-ui
v1.4.1
Release Name: CTK 1.4.0
Support: Stable Release
Release Date: 15th April, 2024
The 1.4.0 version of CTK includes the following new features:
New Features in CTK 1.4.0 release
Quality Assessment Report is now available for Quality Assessment Collections. This report is eligible for review, similar to the Compliance Collection report.
Added a new CTK Landing page
Added Terms & Conditions consent popup for partners during login. If a partner does not provide consent, they will be automatically logged out.
SBI Testcases Enhancements
Added a negative SBI testcase SBI1196 where Discover request attributes are in UPPER CASE
Added testcases(SBI1197, SBI1198 and SBI1199) where bioSubTypes is optional in RCapture request
Enhanced all SBI schemas by adding "Additional Properties" as "false" in all nested objects as well. This will disallow any extra attributes at nested levels.
Community reported issue in the CTK UI GitHub repository is fixed - Android SBI CTK Check Device Status failed: SBI1028, SBI1029
In the trust validation process, we’ve now incorporated an additional check for the Organization Name. This check involves verifying both the logged-in user’s organization and the Subject Organization specified in the certificate. By doing so, we enhance the security and reliability of our validation procedures.
Responses from SBI RCapture will now be encrypted and stored in the CTK database.
In response to a community-reported issue, CTK now sends the ‘previousHash’ as the SHA256 hash of an empty UTF-8 string, rather than simply an empty string.
The attributes, "requestedScore" and "qualityScore" currently support floating point numbers in CTK schemas and testcases.
ABIS Testcases Enhancements
Added new ABIS DataShare related testcases ABIS3030, ABIS3031. ABIS3031 is inactive in this release since it needs some changes in kernel-auth-adapter.
Enhanced all ABIS schemas by adding "Additional Properties" as "false" in all nested objects as well. This will disallow any extra attributes at nested levels.
SDK Testcases Enhancements
Enhanced all SDK schemas by adding "Additional Properties" as "false" in all nested objects as well. This will disallow any extra attributes at nested levels.
Technical Enhancements
Added a Batch Job for Archival of oldest X test runs per collection to an archive table. This X is configurable.
API documentation
Create separate repository for CTK test cases.
CTK 1.4.0 test with latest released code of Mock MDS, Mock SDK and Mock ABIS
Capture BQAT version and other details in Quality Assessment Report
Fixed bugs identified in Security Testing of CTK
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
Post installation, follow the setup steps available here.
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices:
The Windows Compliance tool kit was tested with the below specifications:
ABIS (Automated Biometric Identification System) Specifications were tested with Fingerprint, Iris and Face modalities as per MOSIP ABIS API specifications.
Secure Biometric Interface (SBI) with Compliance testcases collection and Quality Assessment testcases collection on below modalities
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
Biometric SDK
Quality Check
Match
Extraction
Conversion
The Android Compliance tool kit app v1.3.0 was tested with the below specifications:
Secure Biometric Interface (SBI) with Compliance testcases collection and Quality Assessment testcases collection on below modalities
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
MOSIP interfaces with an Automated Biometric Identification System (ABIS) to perform de-duplication of a resident's biometric data. A country may use multiple ABISs for the same biometric data and evaluate the best ABIS based on de-duplication quality. ABIS is used for 1:N de-duplication. For 1:1 authentication, Biometric SDK is used. MOSIP does not recommend using an ABIS for 1:1 authentication.
Test cases have been tested with MOSIP mock ABIS for compliance with the MOSIP specifications across 29 test cases.
Out of scope: Real ABIS testing in CTK 1.3.0
The Secure Biometric Interface (SBI) is used to interface with the biometric devices. The Compliance tool kit was tested to ensure that the interface built by the device provider is following the specifications and security rules defined in the SBI spec. The device hardware security features are not tested as a part of Compliance tool kit.
The Android CTK app v1.3.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 55 test cases. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI.
The Android CTK app v1.3.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 64 test cases. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI and real registration face SBI.
The Windows CTK 1.3.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 55 authentication spec test cases.
The Windows CTK 1.3.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 76 registration spec test cases.
Out of scope: Real devices testing on Windows and android CTK v1.3.0.
The SDK implementation has been tested to support quality check, match, extraction, and conversion of biometrics. Test cases have been tested with MOSIP mock SDK.
Out of scope: Segmentation testing and Real SDK testing.
CTK-Keycloak login field names in Arabic are not appearing in RTL.
Forgot Password option is not working in CTK login page.
Error message should be user friendly in CTK sign-in page.
Column name is showing as 'View report'
Getting 500 error for endpoint /v1/authmanager/authorize/invalidateToken in development environment.
mosipqa/compliance-toolkit-service:1.3.0
mosipqa/compliance-toolkit-ui:1.3.0
mosipqa/postgres-init:1.2.0.1
mosipqa/postgres-init:1.2.0.1
mosipqa/postgres-init:develop
mosipid/config-server:1.1.2
mosipid/kernel-auditmanager-service:1.2.0.1-B1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipqa/authentication-service:1.2.0.1
mosipid/kernel-keymanager-service:1.2.0.1-B2
mosipid/keycloak-init:1.2.0.1-B2
mosipid/partner-management-service:1.2.0.1-B3
mosipqa/partner-onboarder:develop
mosipid/kernel-notification-service:1.2.0.1-B1
mosipqa/keycloak-init:1.2.0.1
mosipqa/minio-client-util:latest
Release Name: CTK 1.2.0
Upgrade From: CTK 1.1.0
Support: Stable Release
Release Date: 14th July, 2023
The 1.2.0 version of CTK includes the following new features:
CTK now supports ABIS testing
CTK now supports BQAT quality check on biomterics captured by SBI devices.
CTK now supports additional ISO validations for SBI after decoding the image.
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1-B2
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
Release Name: CTK 1.1.0
Upgrade From: CTK 1.0.0
Support: Stable Release
Release Date: 19th May, 2023
The 1.1.0 version of CTK includes the two new features:
Multiple Language support in CTK
Android SBI testing
Multiple Language support in CTK
CTK will now support the application in multiple languages.
While logging in, the partner can select a language from the dropdown.
Therafter, the application will be displayed in the selected language.
By default, CTK will support three languages- English, French and Arabic.
Android SBI testing
CTK will now support Android SBI testing using the Android CTK App.
The basic features such as,
Create a Project
Create a Collection
Run a Collection
View Details of a Test Run
Add Biometric Data
are available as part of the releases.
The current version can be used by the device and biometric SDK vendors to test their SBIs and SDKs.
As a part of the SBI test suite, we support the verification schema and signature verification of,
Interfaces
Device discovery
Device info
Capture
RCapture
Certification Level
L0
L1
Biometric Modalities
Fingerprints
Iris
Face
As a part of the SDK test suite in the current version, we support the verification of schema and interface level verification for,
Interfaces
Initialization
Quality Check
Matcher
Extractor
Converter
Biometric Modalities
Fingerprint
Iris
Face
The detailed list of the test cases for SBI and SDK in the 1.1.0 version of the Compliance Tool Kit are available here:
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1-B2
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices:
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
The Android Compliance tool kit App v1.1.0 was tested with the below specifications:
Secure Biometric Interface (SBI)
The Windows Compliance Tool kit was tested with the below specifications:
Secure Biometric Interface (SBI)
SDK
Quality Check
Match
Extraction
Conversion
The Secure Biometric Interface (SBI) is used to interface with the biometric devices. The Compliance Tool kit was tested to ensure that the interface built by the device provider is following the specs and security rules defined in the SBI spec. The device hardware security features are not tested as part of Compliance Tool kit.
The Android CTK app v1.1.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 55 test cases.
Test cases specific to the quality and user interactions have been tested with MOSIP Android mock SBI.
The Android CTK app v1.1.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 64 test cases.
Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI and real registration face SBI.
The Android CTK app v1.1.0 with real Android registration face SBI has been tested for compliance with the specification only for registration face device.
The Windows CTK v1.1.0 with MOSIP Windows Mock SBI has been tested for compliance with the specifications across 55 authentication spec test cases.
The Windows CTK v1.1.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 76 registration spec test cases.
Out of scope: Real devices testing in windows CTK.
The SDK implementation has been tested to support quality check, match, extraction, and conversion of biometrics. Test cases have been tested with MOSIP mock SDK.
Out of scope: Segmentation testing and Real SDK testing
mosipqa/compliance-toolkit-service: 1.1.0
mosipqa/compliance-toolkit-ui: 1.1.0
mosipqa/postgres-init: 1.2.0.1
mosipid/postgres-init :1.2.0.1-B2
mosipid/config-server: 1.1.2
mosipid/kernel-auditmanager-service: 1.2.0.1-B1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipqa/authentication-service: 1.2.0.1
mosipid/kernel-keymanager-service: 1.2.0.1-B2
mosipid/keycloak-init: 1.2.0.1-B2
mosipqa/partner-management-service: 1.2.0.1
mosipqa/partner-onboarder: develop
mosipid/kernel-notification-service: 1.2.0.1-B1
mosipid/keycloak-init: 1.2.0.1-B2
mosipid/mosip-keycloak: 16.1.1-debian-10-r85
mosipqa/keycloak-init: develop
Release Name: CTK 1.3.0
Upgrade From: CTK 1.2.0
Support: Stable Release
Release Date: 5th January, 2024
Note:
On January 25th, 2024, the mosip-compliance-toolkit tag has been updated from v1.3.0 to v1.3.1 in order to resolve a bug in the BiometricsQualityCheckValidator during the conversion of bioScore into bioScoreRange.
Furthermore, on February 12th, 2024, an update was made to the mosip-compliance-toolkit tag from v1.3.1 to v1.3.2. This update aims to address the issue of missing table names in the ddl.sql located within the db_scripts folder.
The 1.3.0 version of CTK includes the following new features:
Enhanced Report Generation and submission capabilities for CTK (Report for Review).
Added Admin login functionality to enable viewing Partner Reports, conducting Test Runs, and approving or rejecting submitted Reports.
Incorporated Quality Assessment testcases using BQAT quality check on biometrics captured by SBI devices.
Additional Hash Validation testcases for SBI to ensure data integrity.
Included support for in CTK.
To know more about the Hash generation logic, read .
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1-B2
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
Release Name: CTK 1.0.0 (Beta)
Upgrade From:
Release Date: 3rd February 2023
The 1.0.0 version of MOSIP’s Compliance Tool Kit is the first patch release on top of the release on top of 0.0.9 version. This release covers similar features as the 0.0.9 version but has additional test scenarios for the SBI, like
Key Rotation Validations
Quality Check Validation of the biometrics captured in SBI
ISO Validation of the ISO data captured from the SBI
The subsequent releases will have more aggressive test scenarios and integration components (like ABIS, Manual Adjudication & Manual Verification systems).
The basic features such as,
Create a Project
Create a Collection
Run a Collection
View Details of a Test Run
Add Biometric Data
are available as part of the releases.
The current version can be used by the device and biometric SDK vendors to test their SBIs and SDKs.
As a part of the SBI test suite, we support the verification schema and signature verification of,
Interfaces
Device discovery
Device info
Capture
RCapture
Certification Level
L0
L1
Biometric Modalities
Fingerprints
Iris
Face
As a part of the SDK test suite in the current version, we support the verification of schema and interface level verification for,
Interfaces
Initialization
Quality Check
Matcher
Extractor
Converter
Biometric Modalities
Fingerprint
Iris
Face
The detailed list of the test cases for SBI and SDK in the 1.0.0 version of the Compliance Tool Kit is available here:
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1-B2
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices:
The Windows Compliance tool kit was tested with the below specifications:
ABIS (Automated Biometric Identification System) Specifications was tested with Fingerprint, Iris and Face modalities as per specifications.
Secure Biometric Interface (SBI)
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
Biometric SDK
Quality Check
Match
Extraction
Conversion
The Android Compliance tool kit app v1.2.0 was tested with the below specifications:
Secure Biometric Interface (SBI)
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
MOSIP interfaces with an Automated Biometric Identification System (ABIS) to perform de-duplication of a resident's biometric data. A country may use multiple ABISs for the same biometric data and evaluate the best ABIS based on de-duplication quality. ABIS is used for 1:N de-duplication. For 1:1 authentication, Biometric SDK is used. MOSIP does not recommend using an ABIS for 1:1 authentication.
Test cases have been tested with MOSIP mock ABIS for compliance with the MOSIP specifications across 29 test cases.
Out of scope: Real ABIS testing in CTK 1.2.0
The Secure Biometric Interface (SBI) is used to interface with the biometric devices. The Compliance tool kit was tested to ensure that the interface built by the device provider is following the specifications and security rules defined in the SBI spec. The device hardware security features are not tested as a part of Compliance tool kit.
The Android CTK app v1.2.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 55 test cases. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI.
The Android CTK app v1.2.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 64 test cases. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI and real registration face SBI.
The Windows CTK 1.2.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 55 authentication spec test cases.
The Windows CTK 1.2.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 76 registration spec test cases.
Out of scope: Real devices testing on Windows and android CTK.
The SDK implementation has been tested to support quality check, match, extraction, and conversion of biometrics. Test cases have been tested with MOSIP mock SDK.
Out of scope: Segmentation testing and Real SDK testing.
After login to CTK Android app, the previous browser tab is not killed. Workaround: Once the popup appears, the user can manually close the tabs.
Newly registered user not landing on the CTK android home page (an intermittent issue observed on Samsung A03 mobile device).
In CTK Android app, UI elements are overlapping with each other (issue observed on Samsung A03 and Oneplus nord AC2001 mobiles because of screen size).
Add project/ collection takes empty spaces as name (validation is missing).
In Android CTK -Encryption Key button is not appearing for Auth projects (Workaround: Partners can download the Encryption Key from the web application.
With Android mock MDS, SBI1067 and SBI1068 testcases for Auth Iris ISO validation failing (issue with Android mock MDS).
mosipqa/compliance-toolkit-service:1.2.0
mosipqa/compliance-toolkit-ui:1.2.0
mosipqa/postgres-init:1.2.0.1
mosipid/postgres-init:1.2.0.1-B2
mosipid/config-server:1.1.2
mosipid/kernel-auditmanager-service:1.2.0.1-B1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipqa/authentication-service:1.2.0.1
mosipid/kernel-keymanager-service:1.2.0.1-B2
mosipid/keycloak-init:1.2.0.1-B2
mosipqa/partner-management-service:1.2.0.1
mosipqa/partner-onboarder:develop
mosipid/kernel-notification-service:1.2.0.1-B1
mosipid/mosip-keycloak:16.1.1-debian-10-r85
| Repositories | Tags Released |
|---|---|
Post installation, follow the setup steps available .
Post installation, follow the setup steps available .
| Repositories | Tags Released |
|---|
Post installation, follow the setup steps available .
Post installation please follow the setup steps available .
mosip-compliance-toolkit
mosip-compliance-toolkit-ui
compliance-toolkit-batch-job
compliance-toolkit-testcases
mosip-config
Scenarios
Mock ABIS
Total
28
Passed
27
Pending
0
Failed
0
NA
1
Test Rate (%)
100%
Pass Rate (%)
100%
Scenarios
Finger
Iris
Face
Total
36
26
40
Passed
36
26
40
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
90%
100%
Scenarios
Finger
Iris
Face
Total
47
24
43
Passed
47
24
43
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
34
26
40
Passed
34
26
40
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
53
27
46
Passed
53
27
46
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
With Mock SDK
Total
65
Passed
65
Pending
0
Failed
0
Test Rate (%)
100%
Pass Rate (%)
100%
Scenarios | Mock ABIS |
Total | 28 |
Passed | 27 |
Pending | 0 |
Failed | 0 |
NA | 1 |
Test Rate (%) | 100% |
Pass Rate (%) | 100% |
Scenarios | Finger | Iris | Face |
Total | 19 | 21 | 15 |
Passed | 19 | 19 | 15 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 90% | 100% |
Scenarios | Finger | Iris | Face |
Total | 29 | 18 | 17 |
Passed | 29 | 18 | 17 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
NA | 1 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | Finger | Iris | Face |
Total | 19 | 21 | 15 |
Passed | 19 | 21 | 15 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | Finger | Iris | Face |
Total | 35 | 21 | 20 |
Passed | 35 | 21 | 20 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | With Mock SDK |
Total | 65 |
Passed | 65 |
Pending | 0 |
Failed | 1 |
Test Rate (%) | 100% |
Pass Rate (%) | 100% |
Scenarios | Finger | Iris | Face |
Total | 19 | 21 | 15 |
Passed | 19 | 21 | 15 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | Finger | Iris | Face |
Total | 29 | 18 | 17 |
Passed | 29 | 18 | 17 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | Finger | Iris | Face |
Total | 29 | 18 | 17 |
Passed | 0 | 0 | 3 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 14 |
Test Rate (%) | 0% | 0% | 100% |
Pass Rate (%) | 0% | 0% | 18% |
Scenarios | Finger | Iris | Face |
Total | 19 | 21 | 15 |
Passed | 19 | 21 | 15 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 14 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | Finger | Iris | Face |
Total | 35 | 21 | 20 |
Passed | 35 | 21 | 20 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 14 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Scenarios | With Mock SDK |
Total | 76 |
Passed | 65 |
Pending | 0 |
Failed | 0 |
N/A | 11 |
Test Rate (%) | 86% |
Pass Rate (%) | 86% |
Issue | Description |
MOSIP-26898 | After login to CTK android app, the previous browser tab is not killed. |
MOSIP-26762 | Newly registered user not landing into CTK android home page (intermittent issue) |
MOSIP-27044 | In CTK Android app, UI elements are overlapping with each other. |
MOSIP-27257 | While initial launch, Android mock SBI is not landing into home page. |
MOSIP-27304 | In Android CTK -'Encryption Key' button is not appearing for Auth projects (Workaround: Partners can download 'Encryption Key' from web application) |
MOSIP-27391 | CTK - UI and Buttons not aligned properly |
MOSIP-27440 | CTK UI Reliability bugs reported in SonarCloud |
Release Name: CTK 0.0.9 (Beta)
Upgrade From: NA (First Release)
Release Date: 1st December, 2022
The 0.0.9 version of MOSIP’s Compliance Tool Kit is the first beta release which covers the essential features to test an SBI and Biometric SDK which follows MOSIP’s biometric specifications. The subsequent releases will have more aggressive test scenarios and integration components (like ABIS, Manual Adjudication & Manual Verification systems).
The basic features such as,
Create a Project
Create a Collection
Run a Collection
View Details of a Test Run
Add Biometric Data
are available as part of the releases.
The current version can be used by the device and biometric SDK vendors to test their SBIs and SDKs.
As a part of the SBI test suite, we support the verification schema and signature verification of,
Interfaces
Device discovery
Device info
Capture
RCapture
Certification Level
L0
L1
Biometric Modalities
Fingerprints
Iris
Face
As a part of the SDK test suite in the current version, we support the verification of schema and interface level verification for,
Interfaces
Initialization
Quality Check
Matcher
Extractor
Converter
Biometric Modalities
Fingerprint
Iris
Face
The detailed list of the test cases for SBI and SDK in the 0.9.0 version of the Compliance Tool Kit is available here:
Artifactory: mosipid/artifactory-ref-impl: 1.2.0.1-B2
Audit manager: mosipid/kernel-auditmanager-service: 1.2.0.1-B1
Auth Manager: mosipid/kernel-authmanager: 1.2.0.1-B1
Key Manager: modipid/kernel-keymanager-service: 1.2.0.1-B1
Partner Management: mosipid/partner-management-service: 1.2.0.1-B1
KeyCloak: mosipid/keycloak-init: 1.2.0.1-B1
Postgres: mosipid/postgres-init: 1.2.0.1-B1
Config Server: config-server: mosipid/config-server: 1.1.2
Notification Service: mosipid/kernel-notification-service: 1.2.0.1-B1
ClamAV: clamav/clamav: latest
MinIO
Post installation please follow the setup steps available here.
mosip-compliance-toolkit |
mosip-compliance-toolkit-ui |
bio-utils |
Imagedecoder |
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices:
Registration devices for iris, face and fingerprint
Authentication devices for iris, face and fingerprint
The compliance tool kit was tested with the below biometric specifications:
SBI
SDK
Quality Check
1:N Match
Extraction
Conversion
The Secure Biometric Interface (SBI) is used to interface with biometric devices. The compliance tool kit was tested to ensure that the interface built by the device provider is following the specs and security rules defined in the SBI spec.
The MOSIP’s Mock SBI has been tested for compliance with the specifications across 37 test cases. Test cases specific to quality and user interactions have been tested with real devices rather than mock.
The MOSIP’s Mock SBI has been tested for compliance with the specifications across 49 test cases. Test cases specific to quality and user interactions have been tested with real devices rather than mock.
The MOSIP’s real devices has been tested for compliance with the specification only for fingerprint devices.
The MOSIP’s real SBI has been tested for compliance with the specifications for iris, face and fingerprint devices.
The SDK implementation has been tested to support quality check, 1:N match, extraction, and conversion of biometrics.
Out of scope: Segmentation testing
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices: Registration devices for iris, face and fingerprint Authentication devices for the iris, face and fingerprint The compliance tool kit was tested with the below biometric specifications:
SBI a. Registration b. Authentication
SDK a. Quality Check b. 1: N Match c. Extraction d. Conversion
The Secure Biometric Interface (SBI) is used to interface with biometric devices. The compliance tool kit was tested to ensure that the interface built by the device provider follows the specs and security rules defined in the SBI spec.
The MOSIP’s Mock SBI has been tested for compliance with the specifications across 48 test cases. Test cases specific to quality and user interactions have been tested with real devices rather than mock.
The MOSIP’s Mock SBI has been tested for compliance with the specifications across 65 test cases. Test cases specific to quality and user interactions have been tested with real devices rather than mock.
The MOSIP’s real devices have been tested for compliance with the specification only for fingerprint and iris devices.
The MOSIP’s real SBI has been tested for compliance with the specifications for iris, face and fingerprint devices.
The SDK implementation has been tested to support quality checks, 1:N matches, extraction, and conversion of biometrics.
Out of scope: Segmentation testing
Scenarios
Finger
Iris
Face
Total
17
18
13
Passed
17
18
13
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
30
18
17
Passed
30
18
17
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
17
18
13
Passed
14
1
0
Pending
0
0
13
Failed
3
17
0
Test Rate (%)
100%
100%
0%
Pass Rate (%)
82%
6%
0%
Scenarios
Finger
Iris
Face
Total
30
18
17
Passed
30
18
17
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios.
With Mock SDK
With Real SDK 1
With Real SDK 2
Total
76
76
76
Passed
66
27
51
Pending
0
0
0
Failed
1
11
16
Not Applicable
9
28
9
Test Rate (%)
88%
50%
88%
Pass Rate (%)
87%
36%
67%
Scenarios
Finger
Iris
Face
Total
14
13
10
Passed
14
13
10
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
22
14
13
Passed
22
14
13
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios
Finger
Iris
Face
Total
14
13
10
Passed
9
0
0
Pending
0
13
10
Failed
5
0
0
Test Rate (%)
100%
0%
0%
Pass Rate (%)
64%
0%
0%
Scenarios
Finger
Iris
Face
Total
22
14
13
Passed
22
14
13
Pending
0
0
0
Failed
0
0
0
Test Rate (%)
100%
100%
100%
Pass Rate (%)
100%
100%
100%
Scenarios.
With Mock SDK
With Real SDK
Total
76
76
Passed
36
27
Pending
9
0
Failed
31
11
Not Applicable
0
28
Test Rate (%)
88%
50%
Pass Rate (%)
47%
36%
