Version 0.15.0
Release Name: Inji Verify v0.15.0
Support: Developer Release
Release Date: 31st October, 2025
Overview
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.
New Features
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.
Repositories: Released/Dependent
Inji Verify
Projects Released
Inji Verify Repo: 4 projects (all these projects are of same version) are as follows:
Compatible modules
The following table outlines the tested and certified compatibility of Inji Verify 0.15.0 with other modules.
Bug Fixes
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).
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.
User Stories
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).
Error handling in /vp-result/{transactionId} API by sending non-200 status codes in response.
Known Issues
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.
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.
Documentation
Last updated
Was this helpful?