You can now issue mDOCs via OpenID for Verifiable Credentials, with X509 certificates!

Start by creating a new X509 root certificate for issuance in the "Trust" page within the dashboard, or using the Certificates API.

When creating an mDOC credential template, you will now need to select the X509 root certificate you created. The root certificate will automatically be used to generate document signing certificates for the issuance of the mDOC credentials.

The expiration for OpenID4VP requests has been increased from 2 minutes to 5 minutes.

The increased expiration time helps prevent failed presentations due to the user taking a bit longer to go through the presentation flow.

You can now issue SD-JWTs via OpenID4VC with X509 certificates!

Start by creating a new X509 root certificate for issuance in the "Trust" page within the dashboard, or using the new Certificates API.

When creating an SD-JWT credential template, you will now be able to select the X509 root certificate you created. The root certificate will automatically be used to generate document signing certificates for the issuance of the SD-JWT credentials.

The mDOC debugger now shows a document selector if a DeviceResponse contains multiple mDOCs. Previously only the first document was selected.

We have also improved the error handling for the mDOC and SD-JWT VC debuggers, showing the internal error message if the parsing failed. Since the tool is used for debugging, it makes sense to display the internal error message.

Try it out in our mDOC debugger or SD-JWT VC debugger.

You can now sign your OpenID4VC presentation requests with X509 certificates!

Users can now create a X509 root certificate for the verification use case in the "Trust" page within the dashboard, or using the new Certificates API.

The root certificate will automatically be used to generate signing certificates for the requests.

Resolved several issues with the invitation page showing an error screen after an invitation was successfully scanned.

The invitation page now correctly handles all states and shows whether an invitation is completed, expired, or could not be found.

For privacy reasons we will show the successful completion screen on the invitation page even if the issuance or verification failed. The completion screen is mostly to indicate to the user that the invitation has been processed by the wallet.

You can now filter DIDComm issuance and verification session based on the didcommConnectionId and didcommInvitationId in the API.

Try it out with the Retrieve DIDComm issuance sessions and Retrieve DIDComm verification sessions endpoints.

Users on the Pro or Custom tier can now create new projects, and edit the members of a project directly from within the dashboard!

While this feature has been available through the API for a while, the same functionlity is now also available in the dashboard.

To create a new project from the dashboard, select the project selector in the top-left corner, and click the + icon. Managing project members can be done in the in the Members page of the Settings tab within a project.

Read more about it in the add projects and members documentation.

When revoking Anoncreds credentials using the Batch revoke credentials endpoint, you can now notify the wallet about the revocation based on the Didcomm Revocation Notification V2 protocol.

This feature is only available for Anoncreds credentials issued over Didcomm that have a Didcomm connection linked to it, so it does not work for credentials that were issued without a Didcomm connection.

To send a revocation notification to supported wallets, set the notifyWallet body parameter to true. An example payload for the batch revoke credentials endpoint that notifies the wallet:

{
  "issuedCredentialIds": ["clu921ps300047eghxvhz33m4"],
  "notifyWallet": true,
}

You can read more in the Batch revoke credentials endpoint documentation.

We're excited to extend our SD-JWT VC debugger, with a new ISO 18013-5 mDL/mDOC debugger, a powerful tool designed for developers working with mDOCs and mobile Driving Licenses (mDLs).

This debugger enables you to:

• Decode mDOC IssuerSigned and DeviceResponse base64url encoded credentials into human-readable format.
• Visualize the structure of the mDOC attributes, including the issuer X509 certificate, issuer signed attributes, and device key.
• Preview images in the mDOC attributes by hovering over the attribute in the editor.

Whether you're a developer implementing mDOCs, or simply curious about the technology behind decentralized identity, this debugger helps you understand the workings of mDOC credentials.

Try it out now and let us know what you think!