Hazelnut update (v5.1.1)

Release date: 2023-05-16

• Fixed issue where VDR could no longer update broken DID Documents.

Full Changelog: v5.1.0...v5.1.1

Hazelnut update 3 (v5.2.1)

What's Changed

• Backport TLS certificate testdata fixes by @reinkrul in #2120
• Didman: VC with invalid subject breaks organization search by @reinkrul #2114
• Log info message when reprocess has finished

Full Changelog: v5.2.0...v5.2.1

Hazelnut Update 2 (5.3.0-alpha.1)

This release implements RFC019 and RFC020 and contains the new EmployeeIdentity authentication means. The means is introduced as a light weight alternative to UZI and IRMA. It has a lower assurance level, but can be used between organizations who trust each others employee enrollment and identification processes.

This release is an alpha.1 pre-release with the goal of vendors trying out the new functionality and provide feedback.

Hazelnut update 1 (v5.2.0)

• Some VDR OpenAPI operations specified application/json+did-document as Content-Type, while they actually returned application/json.
  This inconsistency is fixed by changing the OpenAPI specification to application/json.
• Diagnostics now show the conflicted document count for DID Documents the node controls. See monitoring documentation for more detail.
• network.connections.outbound_connectors on /status/diagnostics has been moved to /internal/network/v1/addressbook.
  Previously it showed only failing connections, now it shows all addresses it will try to connect to (regardless it's already connected to them or not).
• Added support for encrypting documents using the JWE standard (for DIDComm support).

Full Changelog: v5.1.0...v5.2.0

Hazelnut release

What's Changed

• Default value of strictmode changed to true.
• Introduced new HTTP-based crypto backend, which allows integration of other key storage backends. It uses a separate service (like a sidecar in Kubernetes) which implements a standardized API. The feature is still experimental, but will become the recommended backend for storing private keys in the next major release. See Storage Configuration for more information.
• Internal storage of VDR has changed. A migration will run at startup. If the node is stopped during this process, DID Documents will have to be reprocessed manually (restore functionality)
• Added audit logging for cryptographic operations (creating a new key pair, signing, decrypting). Refer to the documentation for more information.
• Added new API authentication method, in which the administrator configures authorized public keys and the API client is responsible for signing JWT using the private key. This new API authentication is preferred over the current method, which will be removed in the next major release.

Full Changelog: v5.0.0...v5.1.0

Coconut update (10)

What's Changed

• Auth: do not escape parameters in rendered IRMA contracts in #1936

Full Changelog: v5.0.9...v5.0.10

Coconut update (9)

What's Changed

• VCR: Don't check VC existence when revoking by @reinkrul in #1913

Full Changelog: v5.0.8...v5.0.9

Coconut update (8)

What's Changed

• A DID Document update could fail if a deactivation had occurred but was not referenced resulting in failed events

Full Changelog: v5.0.7...v5.0.8

Coconut update (7)

What's Changed

• Allow multiple incoming connections from the same IP

Full Changelog: v5.0.6...v5.0.7

Coconut update (6)

Fixes Irma configuration

Full Changelog: v5.0.5...v5.0.6