Fixed an issue where removing a CSR would remove the associated signing key, even if the CSR already reached the imported status. It now only removes associated signing key if the CSR has not reached the imported status yet.

With this release, we are adding experimental support for ETSI Lists of Trusted Entities (LoTEs).

A LoTE is a digitally signed list of trusted entities, published as part of the European Digital Identity (EUDI) trust framework. Instead of manually adding individual X.509 certificates for each trusted entity, you can point to a LoTE URL and Paradym will automatically fetch the list, verify its signature, and extract the certificates it contains. Read more about how this feature works on our documentation.

This feature is based on standards that are still in development and is therefore experimental. It is subject to change, so please use it with caution.

Fixed an issue where you could link Trusted Issuers from a different project to a Presentation Template using the API.

There have been no cross-project usages.

OpenID4VC Verification sessions now have a new requestRetrieved state, allowing you to react to the user having retrieved the verification request.

This can be useful if you want to hide the deeplink or QR after is has been clicked/scanned, to prevent the user from scanning it multiple times.

The new state value can be subscribed to through webhooks using the new openid4vc.verification.requestRetrieved event. You can read more in the webhooks documentation. If you want to use the new event but only subscribe to specific events for your webhooks, you should update the webhook to also listen to the new request retrieved event.

You can now import X.509 certificates where the hash algorithm uses a different length than the key size. This means you can import an X.509 certificate with a P-256 that is signed using ECDSA with SHA-384 or SHA-512 hashing algorithms. ECDSA certificates signed by Paradym will still always use ECDSA with SHA-256 when using the P-256 key type.

With this release, we are expanding the OpenID4VC Issuance capabilities when using an Attribute Provider. The Attribute Provider can now defer the issuance of a credential, in case it is not ready yet. For more information, please check the Attribute Providers documentation.

To make getting started with verifications easier, we've added pre-made presentation templates for verifying Person Identification Data (PID) and Mobile Driving Licences (mDL).

You can select these templates directly from the dashboard when creating a presentation template, and adjust the requested attributes to fit your use case.

The default expiration time for OpenID4VC verification requests and issuance offers has been increased from 5 to 15 minutes.

For both cases, you can now optionally provide an expiration time using the new expirationInMinutes field when creating a verification request or credential offer.

When importing an externally signed certificate for a Certificate Signing Request, you can now include intermediate certificates that form part of the certificate chain. This allows you to work with certificate authorities that use multi-level PKI hierarchies, where the leaf certificate is not directly signed by the root certificate.

Intermediate certificates can be provided via the parentCertificates field when importing a certificate throug hthe API. When improting a certificate through the dashboard, it can be provided as a PEM-encoded chain in the certificate field. The certificates should be ordered from leaf-adjacent to root-adjacent. Any root certificate included in this list will be ignored.

To learn more, please check out the Certificates documentation.

With this release, we're introducing two new features that allow you to integrate your OpenID4VC issuance flow with existing systems: Authorization Servers, and Attribute Providers.

Authorization servers are external OAuth 2.0 servers that you can integrate with Paradym to add an additional layer of authentication during the credential issuance process. When an authorization server is configured, users must authenticate with that OAuth 2.0 server before they can receive their credentials. This allows you to gate credential issuance behind your own authentication system or a third-party identity provider.

Attribute providers are external HTTPS endpoints that Paradym can call during OpenID4VC issuance to fetch attribute values for a credential. This lets you keep your source of truth in existing systems and populate credentials dynamically, instead of sending all attribute values when creating an offer. This avoids storing any attribute data in Paradym at all.

To learn more about these features, please check out the Authorization Servers and Attribute Providers documentation.