Version 0.14.0
Release Version: v0.14.0
Release Type: Developer Release
Release Date: Coming Soon!
Overview
Inji Certify v0.14.0 introduces key enhancements to credential issuance workflows, interoperability, and user experience. This release focuses on strengthening OpenID4VCI flows, expanding support for emerging credential formats, and improving system usability and integration capabilities.
Major updates include support for presentation during issuance, mDoc/mDL credentials, Pre-Authorized Code flow, enhanced error handling, QR code embedding in credentials, and seamless integration with MOSIP for data-driven credential generation.
Major Highlights / Features
Presentation during Issuance Introduced a new issuance mode enabling residents to present an existing Verifiable Credential to obtain another credential.
Pre-Authorized Code Flow Enabled a simplified issuance flow where users can securely download credentials using a pre-authorized and transaction code.
Support for Issuance in mDoc/mDL Format Added support for issuing Verifiable Credentials in standardized mDoc/mDL formats.
Error Message Revamp Improved the error handling framework with clearer, more structured, and developer-friendly messages.
MOSIP Identity Plugin Integration Integrated with MOSIP APIs to fetch identity data and generate Verifiable Credentials within Certify.
Embedding Data in QR Code for VC Issuance Enabled Claim 169 compliant data embedding within QR codes for secure credential download and verification.
Learn more about all features: Click here to explore the detailed feature documentation.
User Stories Released
Feature
Description
JIRA
Pre Authorized Code Flow
Enables credential issuance without login using a pre-authorized code.
Presentation During Issuance
Enables credential issuance by requiring the user to present an existing Verifiable Credential as proofs.
Issuance of Verifiable Credentials with QR code
Issuing VC with QR code in compliant of claim 169 specification
Enhance Error Message
Improve Error Message Handling for System Integration and Automation
Enable certify to Issue MOSIP UIN as VC
Enable certify to convert and issue MOSIP UIN as verifiable credentials
Bug Fixes
JIRA
Description
Getting 401 error when /issuance/credential API is hit pointing to esignet-1.7.0V
Remove claims validation for mDoc request as claims are optional
Issuer and verification method value is pointing to mosip repo instead of inji in status list credential response
Error message should be user friendly when invalid request is passed - add credential config API
Error code and error messages to be different
VC fetch with VID is failing in Mosipid Usecase
Error message is not proper when render template id is mismatch in DB and config
Error messages are not user friendly when {{url}}/issuance/credential API is executed without context value
Error message is not proper for sunbird and Mosipid use case with 2.0 model context
Error messages difference in few scenarios in Sunbird and MOCK Use cases
Known Issues
Below is the list of known issues related to the release v0.13.0. To access all known issues related to Inji Certify please click here
JIRA
Description
Error messages mismatch in mdoc-mdl usecase(PDI)
CSR Certificate Upload via Automation Causes DID kid Mismatch and VC Verification Failures
Upload ca cert for ecck1 signalgo is failing
Improper Validation in Status Update Endpoints
Generate token API is failing with unkown_error
Repository Released
Repositories
Tags
inji-certify
v0.14.0
inji-config
v0.14.0
keymanager
v1.4.0
digital-credential-plugin
v0.6.0
mosip-functional-tests
Compatible Modules
Documentation
Feature Documentation
Local Setup
API Documentation
Test Report
Last updated
Was this helpful?