v3.2

• The latest APIs are now used during the tests: Authorisation API v4, DID Registry API v5, Ledger API v4, Trusted Issuers Registry API v5, Trusted Schemas Registry API v3 and Trusted Policies Registry API v3.
• The following credential types have been renamed:
  • CTWalletSameInTime → CTWalletSameAuthorisedInTime
  • CTWalletCrossInTime → CTWalletCrossAuthorisedInTime
  • CTWalletSameDeferred → CTWalletSameAuthorisedDeferred
  • CTWalletCrossDeferred → CTWalletCrossAuthorisedDeferred
  • CTWalletSamePreAuthorised → CTWalletSamePreAuthorisedInTime
  • CTWalletCrossPreAuthorised → CTWalletCrossPreAuthorisedInTime
• New Holder Wallet and Issue to Holder pre-authorised and deferred flows with CTWalletSamePreAuthorisedDeferred and CTWalletCrossPreAuthorisedDeferred types.
• The APIs and libraries now support the update Verifiable Attestation schema (2024-01) (VCDM 1.1):
  • issuer can be a URI or an object
  • credentialSubject can contain single or multiple subjects
  • proof is removed
  • evidence can contain single or multiple evidences
• Bug fixes:
  • Follow PEX v2 specifications regarding the path properties, fix JSONPath values. Please make sure to update the path in your presentation submissions accordingly.
  • Share 3 valid VCs during the Verifier tests, as required by the presentation definition.
  • Use nonce defined by the client in the Verifier tests' VP JWT.

v3.1.1

• Improve VCI user authentication capabilities

v3.1

• Credential Request for examples changed into Content-Type of application/json.
• URI Query Parameter parsing for hierarchical data has been aligned with RAR specification. More details can be found from URL Encoding.
• Improved documentation related to ID Token authentication.
• Documented credential_offer_uri

v3.0

• Initial release