Version 0.12.0

Release Version: 0.12.0

Release Type: Developer Release

Release Date: 26th August, 2025

Overview

Inji Certify v0.12.0, brings significant enhancements in credential issuance, revocation, and cryptographic support. This release continues our commitment to aligning with emerging standards while providing issuers with flexible configuration and integration capabilities.

Major Highlights/ Features

• Credential Formats – Draft Implementation

  • SD-JWT and JWT support: Draft implementation enabling issuers to issue credentials in Selective Disclosure JWT (SD-JWT) format, expanding interoperability across wallets. Refer to feature description to know more about this feature
• VC Configuration & Binding

  • Configurable VC Type: Issuers can now configure the VC Type dynamically, providing greater flexibility for different issuance use cases. Refer to feature description for more details.
  • DID Binding with did key🔑 Added support for binding credentials to did:key, enhancing decentralization and cryptographic agility.
  • DID Binding with did:web for kid generation: Introduced support for did:web and automated key ID (kid) generation to enable smooth VC issuance in SD-JWT format.
• Revocation – Draft Implementation

  • VC Revocation: Initial draft implementation of revocation capabilities, allowing issuers to mark credentials as revoked and support verifiers in checking credential status. Refer to feature description for more details.
• Cryptography & Data Integrity

  • Data Integrity Support: Added support for W3C Data Integrity Proofs, providing a standards-based mechanism for ensuring verifiability of issued credentials.
  • ECC R1 Curve Support: Extended cryptographic suite with support for Elliptic Curve secp256r1 (P-256), enabling broader adoption and compliance. Refer to feature description for more details.

Note:

• When configuring the VC type, ensure that the didUrl value in the config file matches the value sent through the API; otherwise, VC issuance will fail.
• The VC Revocation feature is enabled by default for all VCs configured in Inji Certify. Configuration options to customise this will be introduced in an upcoming release.
• VC Revocation and SD-JWT support are released as draft features. They are marked as draft since additional enhancements are still in progress to enable the complete end-to-end flow and to complete comprehensive regression testing.

User Stories Released

Feature	Description	JIRA
Addition/Configuration of Verifiable Credential Type via API post onboarding	Enabling issuer configure new VC types based on the requirement at any time	INJICERT-769
	Enabling additional validation to support the configuration of VC type addition	INJICERT-1036
Revocation of VC	Searching VC to be revoked	INJICERT-1116
	Revoking VC through API	INJICERT-792
Support for VC Issuance with SD-JWT format	Enable Trust Element in VC Format (SD-JWT) Using did:web in iss Attribute	INJICERT-1060
	Issuing VC in SD-JWT Format	INJICERT-61
	Enabling key manager to support did:web binding for VC signing	MOSIP-41756
Data Integrity Proof	Support for W3C Data Integrity Proofs	INJICERT-1033
Code Refactoring	Refactoring code to enhance the code quality of the application	INJICERT-978 INJICERT-768
Signing VC with ECC R1 Algorithm	Extending application’s capability of VC signing and providing support to sign with ECC R1 algorithm	INJICERT-977
DID integration for VC	Allows credentials to be cryptographically bound to a DID, ensuring stronger identity association and verifiability	INJICERT-522

Bug Fixes

JIRA	Description
INJICERT-1184	StatusListCredential in credential status of VC is not accessible
INJICERT-1178	Resolved an issue where certain test cases were failing with a java.lang.NullPointerException error.
INJICERT-1160	Fixed a bug related to VC download for land registry VC type
INJICERT-1156	Issue related to deploying Inji Certify with docker resolved
INJICERT-1155	resolved issue related to VC issuance post the DB changes introduced as part of the new feature change
INJICERT-1120	When credential config APIs used to add new credential type, we need to still update signature in git properties
INJICERT-903	aud in Access Token Uses containsAll Instead of contains
INJICERT-544	Certify doesn't give the @context of the VC it's downloading
INJICERT-324	VC download is failing with credential type "LifeInsuranceCredential"
INJICERT-298	VC download is failing with signature alg (ES256) supported values mentioned in well-known response
MOSIP-42537	Incorrect representation of x5c field in JWT header

Known Issues

Below is the list of known issues related to the release v0.12.0. To access all known issues related to Inji Certify please click here

JIRA	Description
INJICERT-1185	Config dependency for did url is still exists
INJICERT-1182	"credentialStatusPurposes" from credential config API is getting overwritten by git configuration
INJICERT-1176	VC fetch is failing for proof_jwt with did:key binding for ES256 signature only

Repositories Released

Repositories	Tags Released
inji-certify	v0.12.0
digital-credential-plugins	v0.5.0
inji-config	v0.10.0
key manager	v1.3.0-beta.4
commons	v1.3.0-beta.3

Compatible Modules

The following table outlines the tested and certified compatibility of <release version> with other modules.

Modules	Version (with tag links)
eSignet	v1.5.1
id-authentication	v1.2.1.0
Sunbird C	v2.0.0
esignet-mock-services	v0.10.1

Documentation

• Feature Documentation
• QA Report
• Local Setup
• API Documentation