Version 0.18.2
Release Name: Inji Verify v0.18.2
Support: Developer Release
Release Date: 13th July, 2026
Overview
We are pleased to announce the release of Inji Verify v0.18.2. Inji Verify 0.18.2 makes verify-service usable as a Maven library dependency, This patch release updates verify-service's build packaging so it can be consumed directly as a Maven dependency by other projects, in addition to running as a standalone service.
The focus of this release is packaging: verify-service now publishes a plain library JAR as its default Maven artefact, alongside its existing executable JAR, with transitive dependencies resolved automatically via the published POM.
It does not introduce new features, but improves stability, correctness, and reliability of existing functionality in the Inji Verify module.
Key Benefits:
Embed verify-service's credential-verification logic directly inside another Java/Maven service
No manual dependency wrangling — transitive dependencies resolve through the published POM
Existing standalone/executable deployment of verify-service is unaffected
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 Service
Compatible modules
The following table outlines the tested and certified compatibility of Inji Verify 0.18.2 with other modules.
Bug Fixes
Below is the list of fixes as part of the 0.18.2 release, You can refer here to look at the list of bugs fixed through this release.
Configure verify-service to generate an additional library JAR - v0.18.2
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
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.
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?