Release Announcement : Inji Certify v1.0.0-alpha.1 is here!

Inji
1

:loudspeaker: Dear Community Members,

We are excited to announce the release of Inji Certify v1.0.0-alpha.1, a major milestone as we move from the OpenID4VCI draft specifications to the finalized OpenID4VCI 1.0 specification! :tada:

This release introduces enhancements to existing features, along with breaking changes to align with the OpenID4VCI 1.0 specification.

Key highlights of v1.0.0-alpha.1:

  • OpenID4VCI 1.0 specification alignment (credential endpoint, well-known metadata, authorization flows)
  • Credential format transition (vc+sd-jwt to dc+sd-jwt)
  • Addition of a Nonce endpoint - c_nonce generation + replay attack prevention, Redis-backed with TTL expiry
  • Pre-authorized credential offer API — now validates credential_configuration_id and claims against issuer metadata
  • Configurable JSON-LD context loader with caching - in-memory caching, host allowlisting, and locally bundled W3C contexts. Faster, safer, no more runtime dependency on external hosts!

:warning: Note: This release is not backward compatible with the earlier OpenID4VCI draft specifications. The vc+sd-jwt format is replaced by dc+sd-jwt, and c_nonce must now be fetched from the new /nonce endpoint instead of the token response. Upgrading is optional but recommended for spec compliance — teams on earlier releases can continue without disruption, with the option to upgrade at a time that suits your roadmap. Please review the Breaking Changes section of the release notes before upgrading.

Refer to our detailed release notes to learn more about what Inji Certify v1.0.0-alpha.1 brings to the community.

These new features will be available in the Collab environment soon for you to try. Stay tuned for further announcements.

For comprehensive information, take a moment to explore our documentation.

Thank you for being part of this exciting journey with us! Keep an eye out for future updates and stay engaged with the Inji community.

Warm Regards,
Likhitha R L
Product Owner - Inji Certify
On behalf of the INJI Team

3 Likes