Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Version: 0.15.2
Name: Inji Verify v0.15.2
4th December, 2025
Version: 0.15.1
Name: Inji Verify v0.15.1
4th November, 2025
Version: 0.15.0
Name: Inji Verify v0.15.0
31st October, 2025
Version: 0.14.0
Name: Inji Verify v0.14.0
30th September, 2025
Version: 0.13.1
Name: Inji Verify v0.13.1
Date: 20th Aug, 2025
Version: 0.13.0
Name: Inji Verify v0.13.0
Date: 24th July, 2025
Version: 0.12.3
Name: Inji Verify v0.12.3
Date: 28th May, 2025
Version 0.11.1
Name: Inji Verify v0.11.1
Date: 12th May, 2025
Version: 0.11.0
Name: Inji Verify v0.11.0
Date: 2nd April, 2025
Version: 0.10.0
Name: Inji Verify v0.10.0
Date: 10th Oct, 2024
Version: 0.9.0
Name: Inji Verify 0.9.0
Date: 5th July, 2024
Version: 0.8.1
Name: Inji Verify 0.8.1 (Patch)
Date: 22nd May, 2024
Version: 0.8.0
Name: Inji Verify 0.8.0
Date: 8th May, 2024
Release Name: Inji Verify v0.15.1
Support: Patch Release
Release Date: 4th Nov, 2025
This patch release for Inji Verify 0.15.1 addresses critical version alignment issues identified in 0.15.0. By updating key dependencies and SDK versions, this release ensures greater stability, compatibility, and a smoother deployment experience.
In 0.15.1, the POM dependency and SDK versions have been aligned and updated for improved stability and compatibility.
Inji Verify Repositories Released:
inji-verify-service -
inji-verify-ui (ref implementation) -
SDK -
API-Test -
The following table outlines the tested and certified compatibility of Inji Verify 0.15.1 with other modules.
Please refer to the list of items covered as part of release.
Release Name: Inji Verify v0.15.2
Support: Patch Release
Release Date: 4th December, 2025
The Inji Verify 0.15.2 patch release includes critical fixes to ensure reliable testing and smooth deployment. This update resolves the expiry issue with non-dynamic QR codes in the UI test rig and addresses gaps in the API Automation smoke tests such that all test cases execute and pass as expected.
vc-verifier POM Dependency
The POM dependency of vc-verifier was 1.5.0-SNAPSHOT. In version 0.15.1, the POM dependency version is 1.5.0.
1.5.0
1.5.0-SNAPSHOT
Inji Verify SDK Version
The Inji Verify SDK version was 0.15.0-beta.23, which was also true for Inji Verify UI. Now published as 0.15.0 and consumed by Verify UI.
0.15.0
0.15.0-beta.23
Inji Verify
Inji Wallet
Inji Web
Pixel-Pass library
vc-verifier library
Expiry of Non-Dynamic QR Codes in INJI-Verify UI Test Rig:
An issue was identified in the INJI-Verify UI test rig, where non-dynamic QR codes intended to remain static for testing purposes were expiring after a certain duration. This behaviour caused interruptions in automated test flows and inconsistencies during repeated verification scenarios.
Fix made: In this release, the expiry logic for non-dynamic QR codes has been corrected to ensure they remain valid for the entire testing lifecycle, enabling stable, repeatable, and reliable UI test executions.
API Automation v0.15.1 | Smoke Test Results and Fix:
During the execution of the 0.15.1 API Automation smoke test suite, no failures were observed. The expected outcome is for all test cases to execute and pass without any skips. The skipped tests indicate underlying issues that require attention. The results showed: T-12, P-8, S-4, F-0.
T (Total): 12 test cases executed
P (Passed): 8 test cases completed successfully
Inji Verify
Inji Verify Repositories Released:
The following table outlines the tested and certified compatibility of Inji Verify 0.15.2 with other modules.
Inji Wallet
Inji Web
Pixel-Pass library
vc-verifier library
S (Skipped): 4 test cases skipped due to configuration or dependency gaps
F (Failed): 0 failures recorded
Fix made: As part of this release, we have now fixed these gaps to ensure that all smoke tests run as intended and achieve a 100% pass rate in subsequent executions.
Release Name: Inji Verify 0.8.1 (Patch)
Support: Developer Release
Release Date: 22nd May 2024
Inji Verify 0.8.1 addresses critical installation issues by fine-tuning the installation script with minor corrections. Additionally, the update to the Helm chart name helm -n $NS install inji-verify mosip/injiverify in the install.sh script ensures seamless deployment.
Repositories
Tags: Released/Dependent
Inji Verify
Pixel-Pass Library
The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Customizability
Verification is performed with a UI and API test rig.
Testing scope has been focused on the below features:
Automation Functional UI.
Automation API Test rig
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. Functional test was performed in combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256:15c2fcdb50bda62c3b6b7b6ed912d63e8944bee0790f2c2198b043438c0bba3d
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256:1c218f4afcda49c8838ad87ee475249fc554e4962ec6afbd02c8a5a4d89f782e
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for the xls file is .
Release Name: Inji Verify 0.11.1 (Patch)
Support: Developer Release
Release Date: 12th May, 2025
Inji Verify 0.11.1 focuses on ensuring seamless interoperability with Inji Mobile Wallet version 0.16.0 (on Android devices) by aligning with the OpenID4VP - Draft 21 specification. This patch incorporates the following key updates required for compatibility with the mobile wallets following OpenID4VP specification (Draft 21):
QR Data Encoding: QR data is now URL-encoded instead of Base64-encoded.
Mandatory vp_formats: When client_metadata is provided, the vp_formats parameter is now mandatory to ensure proper format negotiation between wallet and verifier.
Important: OpenID4VP – Cross-Device Flow feature is not supported on iOS devices, currently it functions only on the Inji Mobile Wallet (v0.16.0) for Android. Support for IOS is coming up soon with next release i.e. Inji Verify v0.12.0.
Note:
We reccommend users to upgrade to Inji Verify v0.11.1 instead of using v0.11.0, as the OpenID4VP Cross-Device Flow does not function as expected in v0.11.0. (Refer to for more details).
Additionally, please note that the OpenID4VP Cross-Device Flow is compatible only with Inji Mobile Wallet v0.16.0. It is not supported with v0.15.0 as the two key updates (QR Data Encoding and Mandatory vp_formats), required for compatibility, have been incorporated starting v0.16.0 of Inji Mobile Wallet.
The following table outlines the tested and certified compatibility of Inji Verify 0.11.1 with other modules.
Below is the list of fixes as part of the 0.11.1 release:
Release Name: Inji Verify v0.13.1
Support: Developer Release
Release Date: 20th Aug, 2025
The Inji Verify 0.13.1 patch release includes critical fixes to ensure smooth deployment and prevent issues encountered in version 0.13.0.
1. Database Upgrade Script Fix:
In version 0.13.0, the db_upgrade script was missing the table creation script verify-vc_submission.sql.This caused the Inji Verify service to fail when upgrading from version 0.12.3 (which already had the database set up), as the required table was not created.
The previous workaround (in 0.13.0) required manually running verify-vc_submission.sql from db_scripts.
Fix: This patch release now includes the missing script in db_scripts, ensuring the table is created automatically during upgrades.
Note: We recommend upgrading directly to Inji Verify v0.13.1 instead of using v0.13.0. If you continue using v0.13.0, you must manually run verify-vc_submission.sql from db_scripts to create the required table.
Inji Verify Repositories: 4 projects (all these projects are of same version) as below:
inji-verify-service -
inji-verify-ui (ref implementation) -
SDK -
API-Test -
The following table outlines the tested and certified compatibility of Inji Verify 0.13.1 with other modules.
Please refer to the list of items covered as part of patch release.
Below is the list of fixes as part of the 0.13.1 release:
The scope of testing is to verify fitment to the specification from the perspective of the following functions:
● Functionality
● Deployability
● Configurability
● Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
16
16
0
0
Test Rate: 100% With Pass Rate: 100%
27
27
0
0
Test Rate: 100% With Pass Rate: 100%
Inji Verify
Inji Wallet
Inji Web
Pixel-Pass library
vc-verifier library
OpenID4VP - Cross device flow is not working in iOS (works only on Inji mobile wallet in Android phones currently). The supported fix will be provided in 0.12.0 which will be out soon.
VC result is incorrectly displayed under the Upload tab When a Verifiable Credential (VC) is scanned using the Scan feature.
VP Verification is not compatible with Inji Mobile 0.16.0
Inji Verify
Inji Mobile Wallet
Inji Web Wallet
Pixel-Pass library
vc-verifier library
The db_upgrade script for version 0.13.0 is missing the table creation script verify-vc_submission.sql. As a result, when upgrading from version 0.12.3 (which already had the database setup), the required table was not created, causing the inji-verify service to fail.
VP Verification was failing for MOSIP National ID VC as there was a case-sensitive mismatch in “type” of config.json.
API automation failure observed for the /vp-result endpoint with 0.13.0 images in the released environment.
Configurability
Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
Testing scope has been focused on sanity around the following features:
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
OVP functionality Verification:
Windows: using Edge, Firefox and Chrome browsers.
Android: using Edge, Firefox and Chrome browsers, 0.16.0 inji-mobile.
iPhone: using Safari, Edge, Firefox and Chrome browsers, 0.16.0 inji-mobile.
MAC: using Safari Edge, Firefox and Chrome browsers.
Below are the results for Upload, Scan and OVP flow functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
The below section provides details on UI Automation by executing MOSIP functional automation Framework.
Total
Passed
Failed
Skipped
10
10
0
0
Test Rate: 100% With Pass Rate: 100%
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: dee1915d76f02b9e85eb0afd14cbcb2b44bacb15
The below section provides details on UI Automation by executing MOSIP functional automation Framework.
Total
Passed
Failed
Skipped
27
27
0
0
Test Rate: 100% With Pass Rate: 100%
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256:0c3e6307334a29a3dc82a15e80fd10ecf5b66b6eb0f8111bc1dff207bab6d933
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of tests passed / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for all the test report files is here.
● Inji Verify Home page
● Verify Scan Feature
● Verify Upload Feature
Below are the combinations that QA verified and Certified Inji Verify:
Upload feature Verification:
Windows using Edge, Firefox and Chrome browsers.
MAC using Safari browser.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel and Safari browser.
Mobile phone Android with front camera 16 megapixel using browsers Chrome.
Mobile phone Android with front camera 8 megapixel using browsers Chrome.
iPhone with 12 megapixel front camera using Safari browser.
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following functions.
● Functionality
● Deployability
● Configurability
● Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
● Default configuration - with 1 language which is English.
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. The functional test was performed in combination with individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included the simulation of multiple identity schema and respective UI schema configurations.
104
68
33
3
Test Rate: 97%, With Pass Rate: 67%
Here is the detailed breakdown of metrics for each module:
Inji Verify UI
Total
104
Passed
68
Failed
33
Skipped
3
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking, and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
● Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100.
● Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100.
Inji-Verify 0.8.0 - Verification - Report
The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
Testing scope has been focused around the below features:\
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers.
MAC using Safari Edge, Firefox and Chrome browsers. .
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel using Chrome, edge, Firefox and Safari browsers.
Windows laptop with a front camera of 2 megapixel using Chrome, edge, and Firefox browsers.
Mobile phone Android with back camera 16 megapixel using browsers Chrome, Edge and Firefox browsers.
Mobile phone Android and Android Tablet with back camera 8 megapixel using browsers Chrome, Edge and Firefox browsers.
Below are the results for Upload and Scan functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Note: The scan feature is not working with the QR code generated from INJI Mobile, but the QR code that is generated with INJI Web is working fine.
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. Functional test was performed in combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag:
SHA:sha256:5e1c2741b64cc729a29a6ac767d48eeef9a9e0a1942028f9d16a1e80c25c6719
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for the xls file:
<TBD>
Release Name: Inji Verify 0.8.0
Support: Developer Release
Release Date: 8th May, 2024
We are excited to announce the release of Inji Verify version 0.8.0! This release introduces several new features like scanning QR code, uploading QR code, and error handling aimed at improving the user experience and functionality of the verification portal. Below are the key highlights of this release:
New Features:
iPhone and iPad with 12 megapixel back camera Chrome, edge, Firefox and Safari browsers.
Verified in low light to scan the QR code
Verified scan with blur, cracked, low quality QR codes was verified
Total
Passed
Failed
Skipped
349
283
66
0
Test Rate: 100%, With Pass Rate: 81%
Total
Passed
Failed
Skipped
10
10
0
0
Test Rate: 100% With Pass Rate: 100%
Configurability
Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
Testing scope has been focused on the below features:
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Same device flow
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows using Edge, Firefox and Chrome browsers.
Android using Firefox and Chrome browsers.
iPhone using Safari, Edge, Firefox and Chrome browsers.
MAC using Safari Edge, Firefox and Chrome browsers.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel using Chrome, edge, Firefox and Safari browsers.
Windows laptop with a front camera of 2 megapixel using Chrome, edge, and Firefox browsers.
Mobile Android phone Tablet with back camera 16 megapixel using browsers Chrome, Edge and Firefox browsers.
iPhone and iPad with 12 megapixels back camera Chrome, edge, Firefox and Safari browsers.
Verified in low light to scan the QR code
Verified scan with blur, cracked, low quality QR codes was verified
OVP functionality Verification with current INJI Verify version:
Windows using Edge, Firefox and Chrome browsers.
Android using Firefox and Chrome browsers.
iPhone using Safari, Edge, Firefox and Chrome browsers.
MAC using Safari Edge, Firefox and Chrome browsers.
Same device flow Verification with current INJI Verify version:
Android using Edge, Firefox and Chrome browsers.
iPhone using Safari, Edge, Firefox and Chrome browsers.
Same Device flow and OVP was verified with INJI Mobile v 0.20.0
Below are the results for Upload, Scan and OVP flow functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Note : OVP flow was verified in 0.20.0 inji-mobile build.
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. Functional test was performed in combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
842
749
93
0
Test Rate: 100%, With Pass Rate: 88%
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
21
21
0
0
Test Rate: 100% With Pass Rate: 100%
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256:3501df0f116ca40faa947e354dbbab6486ca0058a6a77a406fdfb3d2c9b86197
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
33
33
0
0
Test Rate: 100% With Pass Rate: 100%
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256:4cdc020be40d6c237f490995d26d1ba7410d93a9e47ee1db4aa42c1bd4f44bd2\
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for the xls file (To be updated):
QR Code Scanning: Users can now scan QR codes directly from their device cameras using the built-in scanning feature. This allows for quick and seamless verification of Verifiable Credentials without the need for manual data entry.
QR Code Upload: In addition to QR code scanning, users have the option to upload QR code files from their devices for verification. This provides flexibility for users who may have QR codes saved as digital files.
Error Handling: Error messages and prompts have been added to provide clearer guidance to users in case of issues such as unsupported QR code formats, unreadable QR codes, or scan session timeouts.
Scan Feature QR Code Compatibility:
QR code versions supported for the scan feature range from v22 and below.
Camera Resolution Requirement:
The device's front or web camera resolution must exceed 8 megapixels.
Cameras should be used in well-lit environments without filters, ensuring proper alignment for optimal scanning.
Upload Feature QR Code Compatibility:
QR code versions supported for the upload feature range from v32 and below.
Repositories
Tags: Released/Dependent
Inji Verify
Pixel-Pass Library
Jira ID
Description
Inji-Verify: Able to upload and validate QR Code when internet connection is off.
Inji-Verify: Upload QR Code is accepting image with two same working QR Codes added in one image.
Inji-Verify: Upload QR Code is accepting image with two different working QR Codes added in one image.
Inji-Verify : Scan is not happening for an invalid QR code
Inji Verify: Unable to scan Sunbird QR code through Mobile/Windows/Mac
Inji Verify: The scan feature is not working in Windows (web-based) for the 1 mp camera
Configurability
Customizability
Verification is performed from both end-user and System Integrator (SI) viewpoints, assessing configurability and extensibility to ensure readiness for deployment in multiple countries. As MOSIP is an “API First” product platform, these aspects are critical.
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Same device flow
Upload Feature Verification:
Windows: Edge, Firefox, Chrome
Android: Edge, Firefox, Chrome
iPhone: Safari, Edge, Firefox, Chrome
Mac: Safari, Edge, Firefox, Chrome
Scan Functionality Verification:
Mac (Laptop, 2MP front camera): Chrome, Edge, Firefox, Safari
Windows (Laptop, 2MP front camera): Chrome, Edge, Firefox
Android (Phone/Tablet, 16MP back camera): Chrome, Edge, Firefox
iPhone/iPad (12MP back camera): Chrome, Edge, Firefox, Safari
Verified QR code scanning in low light
Verified scanning with blurred, cracked, and low-quality QR codes
OVP Functionality Verification (current INJI Verify version):
Windows: Edge, Firefox, Chrome
Android: Edge, Firefox, Chrome (0.19.0 INJI-mobile)
iPhone: Safari, Edge, Firefox, Chrome (0.19.0 INJI-mobile)
Mac: Safari, Edge, Firefox, Chrome
Same Device Flow Verification (current INJI Verify version):
Android: Edge, Firefox, Chrome (0.19.0 INJI-mobile)
iPhone: Safari, Edge, Firefox, Chrome (0.19.0 INJI-mobile)
Results for Upload, Scan, and OVP flow functionality were validated across Windows, Android phone, Mac, Android Tablet, iPad, and iPhone with various browsers.
Note: OVP flow supports only the 0.19.0 inji-mobile build.
A persona-based approach was adopted for IV&V, simulating real-world scenarios. Personas represent user types and help determine relevant use cases. Testing addressed:
Functionality
Deployability
Configurability
Customizability
Verification methods varied based on how each need was addressed.
Verification was performed on the following configuration:
Default configuration with 1 language:
English
Functional testing followed a black box approach, covering individual modules and integration, with test data aligned to user stories. Coverage included GUI, system, and end-to-end flows across multiple configurations, simulating various identity and UI schema configurations.
655
562
93
0
Test Rate: 100%, Pass Rate: 85%
MOSIP functional automation framework was used for UI automation.
17
17
0
0
Test Rate: 100%, Pass Rate: 100%
Functional and test rig code base branch used for these metrics:
Hash Tag: sha256:52554ad1062b28e67973e422f046bbc4b49ddad525498017996ed100422d1915
29
29
0
0
Test Rate: 100%, Pass Rate: 100%
Functional and test rig code base branch used for these metrics:
Hash Tag: sha256:7c6529869cec006ae825ed85cc9af57818db11f3ed738de05e71bc9f31dfd532
Manual and automation testing metrics are derived from defect density, test coverage, execution coverage, tracking, and efficiency.
Passed Test Cases Coverage: (Number of passed tests / Total executed) × 100
Failed Test Cases Coverage: (Number of failed tests / Total executed) × 100
GitHub link for the XLS file is here.
The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
Testing scope has been focused around the below features:
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers.
iPhone using Safari, Edge, Firefox and Chrome browsers.
MAC using Safari Edge, Firefox and Chrome browsers.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel using Chrome, edge, Firefox and Safari browsers.
Windows laptop with a front camera of 2 megapixel using Chrome, edge, and Firefox browsers.
Mobile phone Android with back camera 16 megapixel using browsers Chrome, Edge and Firefox browsers.
Mobile phone Android and Android Tablet with back camera 8 megapixel using browsers Chrome, Edge and Firefox browsers.
OVP functionality Verification:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers, 0.16.0 inji-mobile.
iPhone using Safari, Edge, Firefox and Chrome browsers, 0.16.0 inji-mobile.
MAC using Safari Edge, Firefox and Chrome browsers.
Below are the results for Upload, Scan and OVP flow functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Note : OVP flow supports 0.16.0 inji-mobile build only
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. Functional test was performed in combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: 3705d872beb6f103a787badd5d1e141937abb14a
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: a1924880ffba43036f8d6ca8faafca2a36962df1
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for more of the reports is .
The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.
Testing scope has been focused on the below features:
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers.
iPhone using Safari, Edge, Firefox and Chrome browsers.
MAC using Safari Edge, Firefox and Chrome browsers.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel using Chrome, edge, Firefox and Safari browsers.
Windows laptop with a front camera of 2 megapixel using Chrome, edge, and Firefox browsers.
Mobile Android phone Tablet with back camera 16 megapixel using browsers Chrome, Edge and Firefox browsers.
iPhone and iPad with 12 megapixels back camera Chrome, edge, Firefox and Safari browsers.
OVP functionality Verification with current INJI Verify version:
Windows using Edge, Firefox and Chrome browsers.
Android using Edge, Firefox and Chrome browsers, 0.17.0 INJI-mobile.
iPhone using Safari, Edge, Firefox and Chrome browsers, 0.17.0 INJI-mobile.
MAC using Safari Edge, Firefox and Chrome browsers.
Below are the results for Upload, Scan and OVP flow functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Note : OVP flow supports 0.16.0 inji-mobile build only
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. Functional test was performed in combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: 7e1352eae4a0c9090bb15c4be234696d88ecf653
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: 1c3dd7f1144efdf7cab078315fc536af0ad6f960
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for more of the reports is .
iPhone and iPad with 12 megapixel back camera Chrome, edge, Firefox and Safari browsers.
Verified in low light to scan the QR code.
Verified scan with blur, cracked, low quality QR codes was verified.
Total
Passed
Failed
Skipped
505
429
76
0
Test Rate: 100%, With Pass Rate: 84%
Total
Passed
Failed
Skipped
10
10
0
0
Test Rate: 100% With Pass Rate: 100%
Total
Passed
Failed
Skipped
27
27
0
0
Test Rate: 100% With Pass Rate: 100%
Verified in low light to scan the QR code
Verified scan with blur, cracked, low quality QR codes was verified
584
511
66
0
Test Rate: 100%, With Pass Rate: 88%
10
10
0
0
Test Rate: 100% With Pass Rate: 100%
27
27
0
0
Test Rate: 100% With Pass Rate: 100%
Release Name: Inji Verify v0.12.3
Support: Developer Release
Release Date: 28th May, 2025
We are thrilled to announce the release of Inji Verify 0.12.3 that enhances Verifiable Credential (VC) verification capabilities and streamlines ease of integration with relying party applications.
1. Inji Verify SDK - OpenID4VP-VP verification component introduces a modular TypeScript component designed to facilitate easy integration of OpenID4VP-VP verification into verifier/relying party applications.
Modular NPM Package: The OpenID4VP-VP verification component is available as a standalone NPM module, promoting modularity and simplifying integration. Developers can incorporate it into their projects without depending on the full Inji Verify repository.
Comprehensive Integration Guide: A detailed is provided, explaining the setup and usage to ensure a smooth integration process. The steps are also available in the .
Framework Compatibility: Currently, this component is compatible exclusively with verifier applications built using React and TypeScript. Support for additional frameworks and languages is planned for upcoming releases.
These flexibilities empowers developers to accelerate their VC verification implementation with minimal setup, enabling faster time-to-market for digital identity-enabled services.
Note: Inji Verify SDK's OpenID4VP-VP verification component supports React version - 18.2.0
Note: The Inji Verify SDK's Scan/Upload component, enabling developers to embed VC verification capabilities into their applications, will be introduced in future releases. Stay tuned!
2. Inji Verify Backend enhancement - Transition to PostgreSQL
The backend has transitioned from an in-memory H2 database to a PostgreSQL database, ensuring persistent and reliable data storage. This enhancement improves data durability and supports more robust backend operations.
With these updates, Inji Verify continues to evolve, offering more secure, adaptable, and user-friendly credential verification solutions.
Note:
To test OpenID4VP Cross-Device Flow both on Android and iOS devices, we recommend users to upgrade to Inji Verify v0.12.3 instead of using v0.11.1 (as this feature works only on Android phones).
Note:
Additionally, please note that the OpenID4VP Cross-Device Flow is compatible only with Inji Mobile Wallet v0.16.0. It is not supported with v0.15.0 as the two key updates (QR Data Encoding and Mandatory vp_formats), required for compatibility, have been incorporated starting v0.16.0 of Inji Mobile Wallet
Inji Verify Repositories: 4 projects (all these projects are of same version) as below:
inji-verify-service -
inji-verify-ui (ref implementation) -
SDK -
API-Test -
The following table outlines the tested and certified compatibility of Inji Verify 0.12.3 with other modules.
Below is the list of known issues. To read in detail and view all the issues related to Inji Verify please click
Below is the list of fixes as part of the 0.12.3 release:
The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Customizability
Verification is performed not only from the end-user perspective but also from the System Integrator (SI) point of view. Hence, the configurability and extensibility of the software are also assessed. This ensures the readiness of the software for use in multiple countries. Since MOSIP is an "API First" product platform, these aspects are critical for its adaptability and scalability.
Testing scope has been focused around the following features:
Inji Verify Home page
Verify Scan Feature
Verify Upload Feature
OVP Flow
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows: using Edge, Firefox and Chrome browsers.
Android: using Edge, Firefox and Chrome browsers.
iPhone: using Safari, Edge, Firefox and Chrome browsers.
MAC: using Safari Edge, Firefox and Chrome browsers.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixel using Chrome, edge, Firefox and Safari browsers.
Windows laptop with a front camera of 2 megapixel using Chrome, edge, and Firefox browsers.
Mobile phone Android with back camera 16 megapixel using browsers Chrome, Edge and Firefox browsers.
Mobile phone Android and Android Tablet with back camera 8 megapixel using browsers Chrome, Edge and Firefox browsers.
OVP functionality Verification:
Windows: using Edge, Firefox and Chrome browsers.
Android: using Edge, Firefox and Chrome browsers, 0.15.0 inji-mobile.
iPhone: using Safari, Edge, Firefox and Chrome browsers, 0.15.0 inji-mobile.
MAC: using Safari Edge, Firefox and Chrome browsers.
Note: OVP flow supports 0.15.0 inji-mobile build only https://mosip.atlassian.net/browse/INJIVER-1086**.**
Below are the results for Upload, Scan and OVP flow functionality with Windows, Android phone, MAC, Android Tablet, iPad and iPhone with different browsers:
Note: OVP flow supports 0.15.0 inji-mobile build only https://mosip.atlassian.net/browse/INJIVER-1086**.**
Persona-based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product or a service in a similar way. Persona-based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software, and thereby determines use cases or scenarios that the customers will execute. The persona needs may be addressed through any of the following.
Functionality
Deployability
Configurability
Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below
Default configuration - with 1 Lang
English
Below are the test metrics by performing functional testing. The process followed was black box testing, which based its test cases on the specifications of the software component under test. Functional testing was performed in a combination of individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, and End-To-End flows across multiple configurations. The testing cycle included the simulation of multiple identity schemas and respective UI schema configurations.
Test Rate: 100%, Pass Rate: 84%
The below section provides details on UI Automation by executing MOSIP functional automation Framework.
Test Rate: 100%, Pass Rate: 100%
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: dee1915d76f02b9e85eb0afd14cbcb2b44bacb15
The below section provides details on UI Automation by executing MOSIP functional automation Framework.
Test Rate: 100%, Pass Rate: 100%
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256:0c3e6307334a29a3dc82a15e80fd10ecf5b66b6eb0f8111bc1dff207bab6d933
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking, and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of tests passed / Total number of tests executed) x 100
Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
Git hub link for all the report files is .
Release Name: Inji Verify v0.15.0
Support: Developer Release
Release Date: 31st October, 2025
We are excited to announce the release of Inji Verify v0.15.0. This version introduces support for the SD-JWT format across all existing features including QR code scanning, QR code upload, and Verifiable Presentation (VP) verification on both same-device and cross-device modes.
Release Name: Inji Verify 0.9.0
Support: Developer Release
Release Date: 5th July 2024
Release 0.9.0 of Inji Verify enhances usability with a mobile-responsive portal, adds support for CBOR QR code decoding, and includes critical bug fixes. It introduces UI improvements using Tailwind CSS, enables PDF scanning with QR codes, and enhances credential display, including expired credentials. These updates aim to improve overall user experience and system functionality.
The scope of testing is to verify fitment to the specification from the perspective of
● Functionality
● Deploy ability
● Configurability
● Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence, the Configurability and Extensibility of the software is also assessed. This ensures the readiness of software for use in multiple countries. MOSIP is an “API First” product platform.
iPhone and iPad with 12 megapixel back camera Chrome, edge, Firefox and Safari browsers.
Verified in low light to scan the QR code
Verified scan with blur, cracked, low quality QR codes was verified
Total
Passed
Failed
Skipped
486
411
75
0
Total
Passed
Failed
Skipped
10
10
0
0
Total
Passed
Failed
Skipped
27
27
0
0
Unable to scan sunbird QR code through Mobile/Windows/Mac.
VP Verification APIs are validating invalid entries.
Unable to scan VP Verification QR Code from Inji mobile.
When a MOSIP VC is downloaded from Inji Web, the verification fails upon uploading the VC.
Inji Verify
Inji Wallet
Inji Web
Pixel-Pass library
vc-verifier library
In OpenID4VP (Cross device)component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
The OpenID4VP (Cross device) component in Inji Verify currently validates a presentation as successful even when a wrong Verifiable Credential (VC) is submitted. As a temporary workaround, implement credential type validation on the Relaying Party (RP) side, by verifying that the received VC matches the expected type defined in the original presentation_definition.
Implementation of Docker Compose for verify-service is yet to be picked up. (This will be taken up as part of 0.13.0 release)
We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
Inji Verify SDK - OpenID4VP-VP Verification (Cross-device flow) component.
Publish ‘OpenID4VP-VP Verification’ component as a separate NPM module.
Integrate Postgres DB with Inji Verify.
Datashare VC verification was failing due to a configuration issue in mimoto which had to be thereby reverted.
When clicking the 'Verify Another QR Code' button in the Upload tab, if the user cancels the file selection window, the application is not redirecting to the previously viewed Uploaded VC result screen.
Inji Verify API test suite consumed expired VCs which lead to failure in certain test scenarios.
VC verification is failing due to data encoding.
Testcase on GetVpTokenForRequest is failing in dev2 env of inji verify API test rig.
UI and API automation test suite is failing after syncing develop branch.
Ability to verify SD-JWT VC using QR Code Scan feature: Inji Verify now supports SD-JWT based Verifiable Credentials (VCs) which is an additional credential format built on the OpenID4VP and OpenID4VCI specifications.
Ability to verify SD-JWT VC using QR Code Upload feature: Beyond live scanning, Inji Verify allows users to upload QR code images containing SD-JWT VCs directly to the portal.
Ability to create request and verify SD-JWT VC using VP Verification feature - Cross Device flow: Inji Verify enables cross-device verification for SD-JWT based VCs, allowing credentials to be securely shared between devices for instance, from a mobile wallet to a desktop verifier.
Ability to create request and verify SD-JWT VC using VP Verification feature - Same Device flow: With support for the SD-JWT Same-Device Flow, Inji Verify allows both the verifier and the wallet to operate seamlessly on the same mobile device.
Ability to view the claims that were disclosed/ not disclosed for SD-JWT VC verification: When verifying SD-JWT based Verifiable Credentials (VCs), Inji Verify clearly indicates which claims were disclosed and which were withheld by the holder during the verification process.
Error Handling: The portal provides robust error handling to guide users in case of VP Submission issues, with appropriate HTTP status codes indicating the type of error.
Note: The Inji Verify UI is a reference implementation to demonstrate orchestration. Developers can selectively embed SDK components in the verifier applications as per their needs.
Inji Verify
Inji Verify Repo: 4 projects (all these projects are of same version) are as follows:
The following table outlines the tested and certified compatibility of Inji Verify 0.15.0 with other modules.
Inji Wallet
Inji Web
Pixel-Pass library
vc-verifier library
Below is the list of fixes as part of the 0.15.0 release, for the complete list refer to the link.
INJI-verify - GetVpRequestWithDID is failing in Dev-int-inji with invalid response.
Many newly added configurations are missing in docker-compose.yml.
INJI-verify – UI testrig Helm chart missing required configurations.
Missing “type” support for SD-JWT VC in verify UI.
INJI-verify - Intermittently we are not able to create QR code for VP verification flow.
INJI-verify - same device flow on IOS with 0.19.0 wallet is not working (long polling issue).
Create test QR codes with SD-JWT format for testing, removing dependency on other modules.
OpenID4VP - Same-Device Flow: Receive and display results of SD-JWT VP verification (testing).
OpenID4VP - Cross Device Flow: Receive and display results of SD-JWT VP verification (testing).
Upload and verify SD-JWT VC via QR code (testing).
Scan and verify SD-JWT VC QR code (testing).
OpenID4VP - Error Handling Scenarios (testing VP verification errors).
Below is a list of some key known issues. For a detailed overview and the complete list of issues related to Inji Verify, please click here.
In OpenID4VP (Cross device) component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
The OpenID4VP (Cross device) component in Inji Verify currently validates a presentation as successful even when a wrong Verifiable Credential (VC) is submitted. As a temporary workaround, implement credential type validation on the Relaying Party (RP) side, by verifying that the received VC matches the expected type defined in the original presentation_definition.
We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
User friendly error message is not displayed for expired session scenario.
OpenIDVP Cross-Device Flow – The OpenID for Verifiable Presentations (OpenID4VP) Cross-Device Flow facilitates secure sharing of Verifiable Presentations (VPs) across different devices, allowing verifiers to request specific credentials and users to share the requested VCs from their digital wallets on one device while interacting with the verifier on another, with verification result displayed in Inji Verify.
Language Selection – Users can now choose their preferred language from multiple international (Portuguese, Spanish, French, English, Arabic, Khmer) and Indian vernacular (Tamil, Hindi, Kannada), enhancing accessibility and usability.
UI Theme Customization – Integrators and countries can now personalize the UI theme to match their branding and preferences.
Server-Side VC Verification – Integration of the vc-verifier library to support Ed25519 and RSA key verification, strengthening security of server-side verifications.
Zoom Slider for Mobile Scanning – A zoom slider is introduced to adjust magnification for better scanning and verification on mobile devices.
Support for W3C VC Data Model 1.1 & 2.0 – Ensuring compatibility with the latest verifiable credential standards.
Upgrading of vc-verifier library (v1.2.0)
VCs with ED25519 Signature 2018 are verifiable.
Usage of universal DID resolver library.
Theme Upgrade - Introducing a sleek gradient-based design as the new default theme for Inji Verify UI. This theme offers a modern and visually appealing user experience, enhancing usability and aesthetic appeal. This theme can nevertheless be customized based on integrators/countries' preferences.
With these updates, Inji Verify continues to evolve, making credential verification more secure, adaptable, and user-friendly!
Inji Verify
vc-verifier library
The following table outlines the tested and certified compatibility of Inji Verify 0.10.0 with other modules.
Inji Wallet
Inji Web
Pixel Pass
Below is the list of known issues. To read in detail and view all the issues related to Inji Verify please click here.
Jira ID
Description
In OVP, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
Unable to scan sunbird QR code through Mobile/Windows/Mac.
VP Verification APIs are validating invalid entries.
Below is the list of fixes as part of the 0.11.0 release:
Jira ID
Description
OpenID4VP Cross Device Verification failing for multiple scenarios
A suitable error message is not displayed for non - supported QR codes (mock mDL).
There is no success toaster message for successful scan.
Success/ Warning/ Error messages is not placed on the top-right of the screen in mobile view.
Arrows to navigate across tabs are not aligned in mobile view.
The FAQ section is either hidden or not visible on Android and iOS devices
1. UI Enhancements
The user interface of Inji Verify has been optimized for mobile devices, offering responsive views that adapt seamlessly to different screen sizes. Users can conveniently access and utilize the scan and upload feature across devices.
Inji Verify has undergone user interface and user experience enhancements based on GenderMag principles, ensuring improved accessibility and usability.
2. CBOR QR Code Support
Support for CBOR-encoded QR codes has been added, expanding compatibility and enabling broader usage scenarios. Inji Verify can now decode the CBOR QR code using the pixel pass library.
3. Tech Upgrades
Inji Verify has transitioned from MaterialUI to the Tailwind CSS library, offering enhanced flexibility and customization options.
4. Critical Bug Fixes
Several critical bugs related to the scan and upload functionalities have been identified and fixed, ensuring smoother user experiences.
5. Support for PDFs Containing QR Codes
Inji Verify now supports various formats, including PDFs that contain QR codes, broadening the range of documents that can be scanned and verified.
6. Credential Display Enhancements
Credential details retrieved from the issuer's well-known configuration include display properties, ensuring a consistent and accurate representation of credential information.
Users can now view expired credentials within the Inji Verify portal.
7. Browser Support
Chrome, Edge, Safari, and Firefox: Full support for both scan and upload features, ensuring a seamless user experience across these popular browsers.
Assumptions or Limitations:
Verification Method: We are assuming the verification method currently only works with DID (Decentralized Identifier). However, it can also be a direct URL key reference. This distinction is crucial for correct implementation and usage. You can look at the specific code handling this verification method here.
This release represents a significant step forward in improving functionality, usability, and compatibility within Inji Verify.
Repository Released
Inji Verify
Pixel-Pass Library
Below is the list of known issues. To read in detail and view all the topics related to Inji Verify please click here.
Inji Verify - In Android the deactivated flashlight feature appears on the scan screen page.
Inji Verify- The scan screen view is not rendering correctly in the Firefox browser.
Inji Verify - When the user uploads a file in an unsupported format, they do not receive the proper error message.
Inji Verify - In Browser Stack, after clicking the 'Scan QR Code' button, the user is not directed to the camera access 'Allow' popup screen.
Inji Verify - If the attribute values are lengthy, text wrapping does not occur when verifying credentials
Inji Verify - After updating the registry value of a sunbird VC, the old QR code is getting validated.
Below is the list of fixes as part of the 0.9.0 release:
Inji Verify - The upload feature is not working on IOS mobile devices.
Inji Verify -The upload feature is not working in the Safari browser.
Inji Verify - Enhancement The user can use the expired QR code; it does not display any error messages.
Inji Verify - Allowed file formats list should be updated with PDF.
Inji Verify - "QR Code uploaded successfully" message is popping up a late compared to the UI.
"Upload Another QR Code" button is displayed instead of "Upload QR Code" button.
● Inji Verify Home page
● Verify Scan Feature
● Verify Upload Feature
Below are the combinations that QA verified and Certified INJI Verify:
Upload feature Verification:
Windows using Edge, Firefox, and Chrome browsers.
Mac using Safari browser.
Scan functionality Verification:
MAC (Laptop) with a front camera of 2 megapixels and Safari browser.
Mobile phone Android with camera 16 megapixel using browsers Chrome.
iPhone with 24-megapixel camera using Safari browser.
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or service similarly. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software, and thereby determines use cases/scenarios that the customers will execute. The persona's needs may be addressed through any of the following.
● Functionality
● deploy ability
● Configurability
● Customizability
The verification methods may differ based on how the need was addressed.
Verification is performed on various configurations as mentioned below.
● Default configuration - with 1 Language.
English
Below are the test metrics by performing functional testing. The process followed was black box testing which based its test cases on the specifications of the software component under test. The functional test was performed in combination with individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple configurations. The testing cycle included the simulation of multiple identity schema and respective UI schema configurations.
253
198
39
16
Test Rate: 93%, With Pass Rate: 83%
Here is the detailed breakdown of metrics for each module:
Inji Verify UI Verification
253
198
39
16
Firefox
Pass
Pass
Pass
In-consistent (Camera resolutions)
Pass
Edge
Pass
Pass
Firefox
Pass
Pass
Pass
Pass
Pass
Edge
Pass
Pass
Firefox
Pass
Pass
Pass
Pass
Pass
Edge
Pass
Pass
Firefox
Pass
Pass
Pass
Pass
Pass
Edge
Pass
Pass
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking, and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
● Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100.
● Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100.
Git hub link for the xls file
Release Name: Inji Verify v0.14.0
Support: Developer Release
Release Date: 30th September, 2025
We are excited to announce the release of Inji Verify v0.14.0, which brings significant enhancements to OpenID4VP - Same Device flow support, SDK modularization and improvements in verification result handling.
INJI-verify - Same device flow for LandStatementCredential VC on Android with 0.20.0 wallet is not working.
INJI-verify - VP verification for LandStatementCredential VC on IOS and Android with 0.20.0 wallet is not working.
Security testing inji-verify (0.14.0): update vulnerable docker image.s
Security testing: inji-verify(0.14.0) : update vulnerable libraries.
Security testing: Inji verify: Non-literal regular expressions constructed from user input can cause excessive CPU usage.
Inji Verify: In Same Device Flow, getting error on screen, after second round of VP submission.
INJI-Verify – Design document with element ID is not provided.
INJI-verify - Element is replaced and causing a failure in uitestrig.
Inji Verify continues polling for status even after an error alert is displayed. Bug Fixes - Inji Verify.
OpenID4VP: Request Verifiable Credentials button is not opening the wallet selection popup in Android Tablet.
INJI-verify – Getting “Failed To fetch” for the Same Device Flow after successful VP submission in Android devices.
INJI-verify - VP verification is failing intermittently.
INJI-Verify – Deployment ReadMe is Outdated. Inji Verify Release.
INJIVER – After clicking the ‘Scan QR Code’ button, the close icon becomes unresponsive when tapped. Inji Verify SDK.
Secuirty testing: inji-verify(0.12.0) - resolve docker vulnerabilities.
Security testing: inji-verify(0.12.0) - update vulnerable libraries.
Security testing: include timeout after VC display - reload page both in QR code scan, upload and VP verification flows.
INJI-verify - Unable to verify two scenarios in OVP flow.
INJI-verify - selected tab is not been highlighted in mobile view.
INJI-VERIFY : there is no success toaster messages for successful scan.
INJI-Verify: Logo Display Issue on Mobile Devices.
Error codes of OVP flow are not matching the expectation.
Sonar analysis: Reliability issues on inji verify -develop branch. Bug Fixes - Inji Verify.
Error handling in /vp-result/{transactionId} API by sending non-200 status codes in response.
INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
The MOSIP UIN VCs generated via reg-client are currently not verifiable through INJI Verify.
Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
Unable to scan VP Verification QR Code from Inji mobile.
When a MOSIP VC is downloaded from Inji Web, the verification fails upon uploading the VC.
Unable to scan QR codes under low light.
While scanning the QR code, the copyright text overlaps with the zoom slider.
When the user clicks on the ellipse, it is not highlighted in grey color.
The Upload and Scan buttons have a white layout at both beginning and the end.
In iOS and Android devices, the 1-2-3 circles in Inji Verify have vertical lines on the edges.
In all browsers of iPhone, verify credentials is not displayed in gradient color.
On all devices, the loading indicator is not displayed as a circle; instead is rotating as an oval or appearing skewed.
In Firefox, the bullet points on the left side of upload page are not displaying correctly.
Scan screen view is reduced (width and height) within the scan area.
Inji Verify - Getting "No MultiFormat Readers were able to detect the QR code." error when the VC PDF from the inji web application is uploaded.
Inji Verify - In Android The deactivated flashlight feature appears on the scan screen page
Allowed file format and Min size displayed at the right bottom of the inji verify screen is missing on uploading QR code whose size is not supported.
Notification pop up asking for camera access should display on the browser itself once user deny the camera access and try to scan the qr code.
Inji Verify - Able to scan a scratched QR code via mobile.
Instruction message displayed on the header of the scanner when camera gets open to scan qr code , is not appropriate.
Instruction message displayed in the inji verify home page on the header of the scanner is not appropriate.
Scan feature is not working with mobile camera less than 8MP.
No option to select back camera in mobile browser while scanning qr code.
Scan feature is not working in windows (web based) for 1 mp camera.
Inji Verify - Sometimes, we are seeing internet not available in the middle of verification.
Inji Verify - The steps while verifying the QR code is not displayed in mobile view.
Mobile view alignment is not properly aligned.
When I am uploading a working QR code i am able to view the data but it successful error message displaying is wrong i.e "Unfortunately, the given credential is invalid!" and is in red color.
Enhancement: The scan QR code button is not highlighted. The messages (error/successful upload) are not properly aligned.
Time and date displayed on card are not proper (localization of time and date are not done).
Getting "QR code uploaded successfully" pop up on result screen.
QR Code or card with QR code generated via Sunbird is not getting uploaded.
Not getting appropriate error message on uploading blurry QR code.
Activate your device camera step is getting selected even while uploading the QR code.
Pass
In-consistent (Camera resolutions)
Pass
Safari
NA
NA
NA
NA
NA
Chrome
Pass
Pass
Pass
In-consistent (Camera resolutions)
Pass
Pass
Pass
Pass
Safari
Pass
Pass
Pass
Pass
Pass
Chrome
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Safari
Pass
Pass
Pass
Pass
Pass
Chrome
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Safari
NA
NA
NA
NA
NA
Chrome
Pass
Pass
Pass
Pass
Pass
1. OpenID4VP Same-Device flow via deeplink: Inji Verify now supports the OpenID4VP Same Device Flow, allowing verifier and wallet to operate on the same mobile device.
Verifier sends an Authorization Request with presentation_definition via deep link.
Wallet authenticates the user, collects consent, and returns a vp_token via redirect (response_mode=direct_post).
Inji Verify parses the vp_token, validates credentials, and displays results with statuses: Valid, Valid but Expired, Invalid.
Multiple VCs displayed in card format, expandable details, color-coded statuses, and JSON download option.
This feature provides a seamless, app-like experience on same mobile device without requiring a second device.
2. Inji Verify SDK- OpenID4VP- VP verification component where same device flow (point 1) functionality is incorporated
Modular NPM Package: : Released as a standalone TypeScript component for seamless integration into verifier/relying party apps.
Easy Integration: Comes with a step-by-step integration guide and README.
Compatibility: Supported for React + TypeScript verifier apps (React 18.2.0); broader framework/language support planned in future releases.
Note: The Inji Verify UI is a reference implementation to demonstrate orchestration. Developers can selectively embed SDK components in the verifier applications as per their needs.
1. OpenID4VP – QR Codes via request_uri: Inji Verify now supports QR codes that reference the Authorization Request via request_uri instead of embedding it directly.
Wallets resolve the request by performing an HTTP GET to the hosted request object.
This reduces QR code size, improves security (request hosted on trusted verifier servers), and alignment with OpenID4VP best practices.
2. DID-based client_id: Aligned with OpenID4VP Draft 23, Inji Verify now supports DID-based client_id values, replacing the deprecated client_id_scheme. This improves interoperability and trust through decentralized identifiers.
3. VP verification results display:
Verification results now display all originally requested credentials, including any newly shared after a missing credential prompt.
Status clearly shown (Valid, Invalid, Valid but Expired) with completion confirmation once all checks are done.
Inji Verify
Inji Verify Repositories: 4 projects (all these projects are of same version) as below:
Inji Verify Service - 0.14.0 Inji Verify service
Inji Verify UI (ref implementation) - https://github.com/mosip/inji-verify/tree/release-0.14.x/verify-ui
The following table outlines the tested and certified compatibility of Inji Verify 0.14.0 with other modules.
Inji Mobile Wallet
Inji Web Wallet
Pixel-Pass library
vc-verifier library
Below is a list of some key known issues. For a detailed overview and the complete list of issues related to Inji Verify, please click here.
In OpenID4VP (Cross device) component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
The OpenID4VP (Cross device) component in Inji Verify currently validates a presentation as successful even when a wrong Verifiable Credential (VC) is submitted. As a temporary workaround, implement credential type validation on the Relaying Party (RP) side, by verifying that the received VC matches the expected type defined in the original presentation_definition.
We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
OpenID4VP Same-Device flow via deeplink, allowing verifier and wallet to operate on the same mobile device.
Integrate OpenID4VP- VP verification component (same device flow) in Inji Verify SDK.
OpenID4VP Draft 23- Implement DID based client id scheme.
OpenID4VP: Authorisation Request via request_uri for did based client id.
Removal of wallet selection panel in OpenID4VP Same device flow (mobile).
Display VC result of all credentials originally requested after missing credentials have been shared from mobile wallet successfully.
Below is the list of fixes as part of the 0.14.0 release:
Data share VC verification is failing.
Timeout error occurs in /vp-request/{request_id}/status() for Same Device Flow on Android after successful VP submission.
VP verification in Cross-Device Flow causes the iOS Inji Mobile app to crash.
VP verification in Same-Device Flow causes the iOS Inji Mobile app to crash.
SDK README on the NPM site is not updated.
Same Device Flow is not fully developed.
Release Name: Inji Verify v0.13.0
Support: Developer Release
Release Date: 24th July, 2025
We are thrilled to announce the release of Inji Verify 0.13.0 that enhances Verifiable Credential (VC) verification capabilities and streamlines ease of integration with relying party applications.
1. Inji Verify SDK- Scan & Upload component: Inji Verify provides modular SDK components that empower verifier (relying party) applications to seamlessly integrate Verifiable Credential (VC) verification workflows—without relying on the full Inji Verify reference application.
Modular NPM Package: The Scan & Upload component is available as a standalone NPM module, promoting modularity and simplifying integration. Developers can incorporate it into their projects without depending on the full Inji Verify repository.
Comprehensive Integration Guide: A detailed is provided, explaining the setup and usage to ensure a smooth integration process. The steps are also available in the .
Framework Compatibility: Currently, this component is compatible exclusively with verifier applications built using React and TypeScript. Support for additional frameworks and languages is planned for upcoming releases.
Note: The Inji Verify UI is provided as a reference implementation to demonstrate how the SDK components can be orchestrated in a full-fledged verifier application. It is not required for adoption. Developers are encouraged to selectively embed only the components relevant to their business and technical needs.
Note: Inji Verify SDK- Scan / Upload component supports React version- 18.2.0
2. Server Setup for VC and VP Proof Verification in vc-verifier library
The vc-verifier library has been integrated into Inji Verify to enable server-side verification of both Verifiable Credentials (VCs) and Verifiable Presentations (VPs).
Originally designed for credential-level cryptographic and schema validation, the library has now been enhanced to support VP proof verification as per OpenID4VP specifications, ensuring end-to-end trust and compliance.
Key Capabilities:
VP Proof Verification for OpenID4VP flows
VC Proof Verification for OpenID4VCI flows
Support for key types: Ed25519VerificationKey2018, Ed25519VerificationKey2020, and RSAVerificationKey2018
Verification Methods: did:key and did:jwk
1. Support for JsonWebSignature2020 with Ed25519 algorithm type for VP verification : VC-Verifier library supports JsonWebSignature2020 with Ed25519 algorithm for Verifiable Presentation (VP) verification, so that we can process VPs secured with this cryptographic standard and ensure broader interoperability for presentation flows.
2. Configuration of DB Parameters: Database parameters like DB Name, DB Schema, and JDBC URL which were hardcoded earlier, are now dynamically configurable, so that deployments can be made more flexible, environment-specific, and manageable through configuration.
3. Integration of Swagger locally with the Inji Verify API service so that developers can easily access and test the API documentation without relying solely on the published Stoplight documentation.
4. Migration all the JSONB fields to TEXT in Inji Verify database so that we can improve database performance, as we are not utilizing JSON-based filtering and TEXT will better suit our use case.
OpenID4VP Draft 21 enhancement by streamlining the authorization response structure and eliminating unnecessary metadata.
Inji Verify Repositories: 4 projects (all these projects are of same version) as below:
inji-verify-service -
inji-verify-ui (ref implementation) -
SDK -
API-Test -
The following table outlines the tested and certified compatibility of Inji Verify 0.13.0 with other modules.
Below is a list of some key known issues. For a detailed overview and the complete list of issues related to Inji Verify, please click
Below is the list of fixes as part of the 0.13.0 release:
Release Name: Inji Verify v0.10.0
Support: Developer
Release Date: 10th Oct, 2024
We are excited to announce the release of Inji Verify version 0.10.0, which brings significant improvements to the platform, including the implementation of OpenID for Verifiable Presentations (OpenID4VP) specifications, enhanced error handling scenarios, and support for new QR code sharing mechanisms. This release also includes crucial bug fixes, Docker Compose enhancements, and scanner library upgrades.
QR Code Handling Enhancements
Previously, JSON-LD VCs embedded in QR codes were dense and difficult to scan. To address this, the QR codes now embed the URL of the VC storage instead of the entire VC. This allows for easier scanning and sharing of credentials. Additionally, a configuration-based approach has been introduced to manage QR code content per issuer and credential type.
The sharing of credentials via QR codes has been streamlined. Users can now scan the QR code from either a physical copy or a smartphone, which redirects to Inji Web to authorize and present the VP to Inji Verify.
Additional Improvements:
Client & Redirect URI Support:
Inji Verify now includes extra fields (client_id & redirect_uri) to handle OpenID4VP requests, redirecting users for authorization through Inji Web.
VC Validation Improvements:
The following table outlines the tested and certified compatibility of Inji Verify 0.10.0 with other modules.
Below is the list of known issues. To read in detail and view all the issues related to Inji Verify please click
Below is the list of fixes as part of the 0.10.0 release:
User friendly error message is not displayed for expired session scenario.
The MOSIP UIN VCs generated via reg-client are currently not verifiable through INJI Verify.
Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
After scanning a QR code, clicking on 'Verify Another QR Code' sometimes causes the camera to freeze with a black screen.
The Verifiable Credential Selection Panel is not set as the default option.
UI Automation README is outdated and not aligned with recent changes.
Add provision to send transactionID for VC submission from the Relying Party.
The Verifiable Credential Panel contains duplicate element IDs.
NPM warning prevents Sonar analysis from being triggered.
Security testing identified a camera access issue in Inji Verify.
Overlapping text appears at the bottom of the screen during the ‘Initiate VP Request’ process.
Unable to verify two scenarios in the OVP flow.
Language selection is not applied consistently across the entire screen.
Button label and layout are misaligned.
Credential & Presentation Expiry Checks
Robust Error Reporting for failed verifications. This enhancement ensures the verifier backend meets security and interoperability standards while maintaining extensibility for evolving DID-based ecosystems.
NPM warnings are preventing the Sonar analysis from being triggered./td>
The MOSIP UIN VCs generated via reg-client are currently not verifiable through INJI Verify.
Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
Integrate Swagger for API documentation in the Inji Verify backend.
Migrate all JSONB fields to TEXT data type.
OpenID4VP Draft 21: Update Authorization Response to remove unnecessary metadata.
On Windows, users do not receive an appropriate error message when uploading a file in an unsupported format.
Users occasionally face difficulty scanning valid Sunbird RC QR codes on mobile devices.
A 502 error is encountered after uploading a PDF file.
Tapping the 'Scan' button on iOS devices makes the scan screen unexpectedly scrollable.
The ‘Download’ button of verified VC is not properly aligned on the UI.
VC sorting functionality in the VP verification- Credential Selection panel is not working correctly.
API tests are failing following the VC Verifier integration.
UI tests are failing after integrating the Scan and Upload SDK.
VP Request QR code generation is failing.
Verification of Datashare VCs is slower than expected.
The API automation report indicates a failure in the 'GetVpTokenForRequest' method.
VC verification fails when the credential is downloaded from the Inji Web application.
VP verification is not compatible with Inji Mobile version 0.17.0 as the sprint build did not have the entire design in place to be compatible.
Inji Verify
vc-verifier library
Inji Mobile Wallet
Inji Web Wallet
Pixel-Pass library
In OpenID4VP (Cross device)component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
The OpenID4VP (Cross device) component in Inji Verify currently validates a presentation as successful even when a wrong Verifiable Credential (VC) is submitted. As a temporary workaround, implement credential type validation on the Relaying Party (RP) side, by verifying that the received VC matches the expected type defined in the original presentation_definition.
We are uploading an invalid QR code, and while it displays an error message stating that the QR code is invalid, the credential details are still visible.
On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
Inji Verify SDK- Scan & Upload component.
Publish Scan & Upload component as a separate NPM module.
VP Proof Verification in VC- Verifier library.
Add support for JSON Web Signature 2020 using Ed25519 algorithm for Verifiable Presentation (VP) verification.
Add support for JSON Web Signature 2020 using Ed25519 algorithm for Verifiable Presentation (VP) verification.
Configure database parameters.
Implement Docker Compose setup for Inji Verify Service.
The online sharing VCs- OpenID4VP flow remains stuck in the loading state for both Upload and Scan methods.
Inji Verify remained unstable for a certain duration.
Multi-language support is not available (enhancement).
After uploading and verifying the QR code, the retrieved data should display the full name as the first field in the VC result area.
Unable to scan the Sunbird QR code on Mobile, Windows, or Mac devices.
User Flow for Sharing:
The user downloads a VC as a PDF or has a physical copy from Inji Web.
The user scans the QR code using Inji Verify.
Inji Verify redirects to Inji Web for authorization, retrieves the VC in VP format, and completes the verification.
Error Handling Scenarios - OpenID4VP
Introduced comprehensive error handling scenarios as per the OpenID4VP specification to ensure robustness during Verifiable Presentation transactions. This ensures that issues such as invalid credentials or expired tokens are handled gracefully with informative error messages.
Docker Compose
This release simplifies deployment with Docker Compose, allowing users to easily set up and configure the Inji Verify environment.
React-scanner-lib Upgrade The React scanner library has been upgraded for improved performance and reliability in scanning QR codes.
ZXing-cpp library
PDF.js Integration
Updation of Pixel Pass library for Sunbird QR Code
To properly manage binary data by unzipping it before sending it back, the Pixel pass library has been updated to ensure backward compatibility of Sunbird QR codes.
Critical Bug Fixes
Several critical bugs have been resolved, including issues with QR code generation and scanning, ensuring a smoother verification experience.
Inji Verify- The alignment on the no internet error screen is not correct on mobile
Inji Verify : Sometimes the error message is not displayed when we try to upload a file of min size.
Inji Verify- The user scan or upload the Expired QR code is getting the success screen
Inji Verify- In android The deactivated flashlight feature is appearing on the scan screen page
Inji Verify- The alignment of the page for uploading and scanning QR codes in the Safari browser is incorrect.
Inji Verify- The scan screen view is not rendering correctly in the Firefox browser
Injiverify- If the attribute values are lengthy, text wrapping does not occur when verifying credentials
Inji Verify- Update the Readme file required for docker-compose
Inji Verify- No error message when camera being disabled and if the camera is not present.
Inji Verify- Back button from scan page is bringing the last event from upload to scan screen.
Inji Verify- Intermittently, the scan pages alignment is not proper.
Inji Verify- The page alignment during scanning on iOS devices is not accurate
Inji Verify- Unable to upload .PNG extension QR codes
Inji Verify- Mobile Homepage Button Redirects to Connection Failure Page in Desktop View
Repositories
Tags: Released/Dependent
Inji Verify
Pixel-Pass Library
Inji Wallet
Inji Web
Jira ID
Description
Upload feature not functioning on Lower-End iPhones in Chrome Browser
Inji Verify - Page Fails to Load on Lower-End iPhones in Safari Browser
Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and Below
QR Code scan fails on Windows devices.
Unable to scan sunbird QR code through Mobile/Windows/Mac
INJIVER- When the user turns on the internet connection, they encounter a 'no internet' error screen."
Jira ID
Description
Able to upload and validate QR Code when internet connection is off.
Enhancement: Upload QR Code is accepting images with two same working QR Codes added in one image.
Inji Verify-In Browser Stack, after clicking the 'Scan QR Code' button, the default image does not appear.
Inji Verify- In Browser Stack, after clicking the 'Scan QR Code' button,the user is not directed to the camera access 'Allow' popup screen
Inji Verify-In Browser Stack, after clicking the 'Scan QR Code' button, the default image does not appear.
Inji Verify-In Browser Stack, after clicking the 'Scan QR Code' button, the default image does not appear