# Version 0.13.0 **Release Name**: Inji Verify v0.13.0 **Support**: Developer Release **Release Date**: 24th July, 2025 ### Overview 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. ### New Features **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 [integration guide](https://docs.inji.io/inji-verify/technical-overview/integration-guides/openid4vp-vp-verification-integration-guide) is provided, explaining the setup and usage to ensure a smooth integration process. The steps are also available in the [SDK's README](https://github.com/mosip/inji-verify/blob/release-0.13.x/inji-verify-sdk/Readme.md).​ * **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 * 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. ### Additional Enhancements: **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. ### Repositories: Released/Dependent | Repositories | Tags: Released/Dependent | | ------------------- | ------------------------------------------------------------ | | Inji Verify | [v0.13.0](https://github.com/mosip/inji-verify/tree/v0.13.0) | | vc-verifier library | [v1.3.0](https://github.com/mosip/vc-verifier/tree/v1.3.0) | ### Projects: Released Inji Verify Repositories: 4 projects (all these projects are of same version) as below: 1. inji-verify-service - [0.13.0 Inji Verify service](https://github.com/mosip/inji-verify/tree/release-0.13.x/verify-service) 2. inji-verify-ui (ref implementation) - [https://github.com/mosip/inji-verify/tree/release-0.12.x/verify-ui](https://github.com/mosip/inji-verify/tree/release-0.13.x/verify-ui) 3. SDK - 4. API-Test - ### Compatible modules The following table outlines the tested and certified compatibility of Inji Verify 0.13.0 with other modules.
ModuleVersion
Inji Mobile Wallet0.17.0
Inji Web Wallet0.12.0
Pixel-Pass libraryv0.6.0
### 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.](https://mosip.atlassian.net/issues/?jql=project%20%3D%20%22INJIVER%22%20AND%20status%20not%20in%20%28Closed%2C%20Canceled%29%20AND%20type%20%3D%20Bug%20ORDER%20BY%20created%20DESC)
Jira IDDescription
INJIVER-1061In OpenID4VP (Cross device)component, after scanning the health insurance QR code in the injiwallet app, it is displaying the life insurance VC.
INJIVER-1131The 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.
INJIVER-1062We 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.
INJIVER-1063On iPhone 8 and iPhone 7, uploading the Injiweb QR code PDF shows an error message.
INJIVER-625Inji Verify - Upload not functioning on Mac Safari Browser Versions 16 and below.
INJIVER-1194INJI Verify SDK should be able to support integration with applications built on platforms beyond React (Typescript) applications, such as Angular, PHP, and others.
INJIVER-1181NPM warnings are preventing the Sonar analysis from being triggered./td>
INJIVER-1069The MOSIP UIN VCs generated via reg-client are currently not verifiable through INJI Verify.
INJIVER-979Long-polling listeners are implemented within the service layer, preventing the backend from scaling effectively in a multi-pod (distributed) environment.
### User Stories
Jira IDDescription
INJIVER-1039Inji Verify SDK- Scan & Upload component.
INJIVER-1123Publish Scan & Upload component as a separate NPM module.
INJIVER-943VP Proof Verification in VC- Verifier library.
INJIVER-991Add support for JSON Web Signature 2020 using Ed25519 algorithm for Verifiable Presentation (VP) verification.
INJIVER-991Add support for JSON Web Signature 2020 using Ed25519 algorithm for Verifiable Presentation (VP) verification.
INJIVER-1073Configure database parameters.
INJIVER-1120Integrate Swagger for API documentation in the Inji Verify backend.
INJIVER-1122Migrate all JSONB fields to TEXT data type.
INJIVER-1144OpenID4VP Draft 21: Update Authorization Response to remove unnecessary metadata.
### Bug Fixes Below is the list of fixes as part of the 0.13.0 release:
Jira IDDescription
INJIVER-940Implement Docker Compose setup for Inji Verify Service.
INJIVER-1171The online sharing VCs- OpenID4VP flow remains stuck in the loading state for both Upload and Scan methods.
INJIVER-1172Inji Verify remained unstable for a certain duration.
INJIVER-148Multi-language support is not available (enhancement).
INJIVER-156After uploading and verifying the QR code, the retrieved data should display the full name as the first field in the VC result area.
INJIVER-237Unable to scan the Sunbird QR code on Mobile, Windows, or Mac devices.
INJIVER-282On Windows, users do not receive an appropriate error message when uploading a file in an unsupported format.
INJIVER-310Users occasionally face difficulty scanning valid Sunbird RC QR codes on mobile devices.
INJIVER-640A 502 error is encountered after uploading a PDF file.
INJIVER-715Tapping the 'Scan' button on iOS devices makes the scan screen unexpectedly scrollable.
INJIVER-910The ‘Download’ button of verified VC is not properly aligned on the UI.
INJIVER-934VC sorting functionality in the VP verification- Credential Selection panel is not working correctly.
INJIVER-1188API tests are failing following the VC Verifier integration.
INJIVER-1189UI tests are failing after integrating the Scan and Upload SDK.
INJIVER-1197VP Request QR code generation is failing.
INJIVER-1199Verification of Datashare VCs is slower than expected.
INJIVER-1185The API automation report indicates a failure in the 'GetVpTokenForRequest' method.
INJIVER-1192VC verification fails when the credential is downloaded from the Inji Web application.
INJIVER-1161VP 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.
### Documentation * [Feature documentation](https://docs.inji.io/inji-verify/overview/features) * [Integration Guide](https://docs.inji.io/inji-wallet/inji-mobile/technical-overview/integration-guide/building-verifiable-credentials-wallet-with-inji-libraries/openid4vp) * [API Documentation](https://mosip.stoplight.io/studio/inji-verify) * [Collab Guide](https://docs.inji.io/inji-verify/functional-overview/releases-1/inji-verify-collab-guide) * [QA Report](https://docs.inji.io/inji-verify/releases/version-0.13.0/test-report)