Version 0.12.0
Last updated
Was this helpful?
Last updated
Was this helpful?
Release Name: Inji Verify v0.12.0
Support: Developer Release
Release Date: Coming Soon
We are thrilled to announce the release of Inji Verify 0.12.0 that enhances Verifiable Credential (VC) verification capabilities and streamlines ease of integration with relying party applications.
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 SDK's README.​
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!
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.0 instead of using v0.11.1 (as this feature works only on Android phones).
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
v0.12.0
Inji Verify Repositories: 4 projects (all these projects are of same version) as below:
The following table outlines the tested and certified compatibility of Inji Verify 0.12.0 with other modules.
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.
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 SDK - OpenID4VP-VP Verification (Cross-device flow) component.
Publish ‘OpenID4VP-VP Verification’ component as a separate NPM module.
Integrate Postgres DB with Inji Verify.
Below is the list of fixes as part of the 0.12.0 release:
Jira ID
Description
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.
inji-verify-service -
inji-verify-ui (ref implementation) -
SDK -
API-Test -
Below is the list of known issues. To read in detail and view all the issues related to Inji Verify please click