Version 0.14.0
Release Name: Inji Verify v0.14.0
Support: Developer Release
Release Date: 30th September, 2025
Overview
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.
New Features
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_definitionvia deep link.Wallet authenticates the user, collects consent, and returns a
vp_tokenvia 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.
Additional Enhancements:
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.
Repositories: Released/Dependent
Inji Verify
Projects: Released
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
Compatible modules
The following table outlines the tested and certified compatibility of Inji Verify 0.14.0 with other modules.
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.
INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
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.
User Stories
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.
Bug Fixes
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.
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.
Documentation
Last updated
Was this helpful?