Skip to content

Releases: nuts-foundation/nuts-node

Hazelnut update (v5.4.0)

20 Jul 07:55
9723d99
Compare
Choose a tag to compare

What's Changed

New features:

  • Introduced support for issuing and receiving credentials over OpenID4VCI (OpenID Connect for Verifiable Credential Issuance).
    If the node's /n2n endpoint runs on port 443, the node will automatically configure its DIDs for OpenID4VCI support.
    If running on another port, additional action is required. See openid4vci documentation for more information.
  • Added certificate info to peer diagnostics.
  • Added last connection error and the date/time of the next connection attempt to the network's address book.

Bug fixes/improvements:

  • Diagnostics now shows correct number of owned conflicted DID document (vdr.conflicted_did_documents.owned_count).
  • Added background job that periodically checks the node's network state and fixes incorrect XOR hashes.
    This can happen in certain high-load cases on Redis.
  • Network peer authentication failures are now logged on debug instead of warn, leading to less chatter.
    To find out what error occurred, you should now look at the network's address book. /internal/network/v1/addressbook
  • When creating new DID documents, the VDR now checks whether the specified controllers actually exist.
  • Helm chart got updated (@henk-hofs-pink).

Full Changelog: v5.3.0...v5.4.0

v5.4.0-rc.2

14 Jul 09:31
ad25152
Compare
Choose a tag to compare

What's Changed (since rc.1)

Full Changelog: v5.3.0...v5.4.0-rc.2

v5.4.0-rc.1

13 Jul 12:34
29eda5c
Compare
Choose a tag to compare

New features:

  • Introduced support for issuing and receiving credentials over OpenID4VCI (OpenID Connect for Verifiable Credential Issuance).
    If the node's /n2n endpoint runs on port 443, the node will automatically configure its DIDs for OpenID4VCI support.
    If running on another port, additional action is required. See :ref:openid4vci for more information.
  • Added certificate info to peer diagnostics.
  • Added last connection error and the date/time of the next connection attempt to the network's address book.

Bug fixes/improvements:

  • Diagnostics now shows correct number of owned conflicted DID document (vdr.conflicted_did_documents.owned_count).
  • Added background job that periodically checks the node's network state and fixes incorrect XOR hashes.
    This can happen in certain high-load cases on Redis.
  • Network peer authentication failures are now logged on debug instead of warn, leading to less chatter.
    To find out what error occurred, you should now look at the network's address book. /internal/network/v1/addressbook
  • When creating new DID documents, the VDR now checks whether the specified controllers actually exist.
  • Helm chart got updated (@henk-hofs-pink).

What's Changed

Full Changelog: nuts-node-v5.3.0...v5.4.0-rc.1

nuts-node-chart-0.0.3

16 Jun 13:17
177490d
Compare
Choose a tag to compare

A NUTS node Helm chart for Kubernetes

Hazelnut update (v5.3.1)

13 Jun 15:53
ff5ac79
Compare
Choose a tag to compare

Release date: 2023-06-13

  • Fixed issue where a Reprocess failed due to missing data

Full Changelog: v5.3.0...v5.3.1

Hazelnut update (v5.2.3)

13 Jun 15:49
8794769
Compare
Choose a tag to compare

Release date: 2023-06-13

  • Fixed issue where a Reprocess failed due to missing data

Full Changelog: v5.2.2...v5.2.3

Hazelnut update (v5.1.2)

13 Jun 15:46
c303cca
Compare
Choose a tag to compare

Release date: 2023-06-13

  • Fixed issue where a Reprocess failed due to missing data

Full Changelog: v5.1.1...v5.1.2

Hazelnut update (v5.3.0)

06 Jun 11:21
4db689b
Compare
Choose a tag to compare
  • Automatically resolving of node DIDs has been removed, since it caused more confusion than it simplified things.
    It was only meant for workshop/demo purposes and not allowed in strict mode, so the impact should be very limited.
    If you didn't configure a node DID but do want to exchange private credentials,
    you now have to configure it explicitly using network.nodedid.
  • The tls.crl.maxvaliditydays config flag has been deprecated. CRLs are now updated more frequently, making this option obsolete.
  • Adds support for RFC019 and RFC020, which describe a new EmployeeIdentity authentication means which allows an employer to make claims
    about the identity of their employees. This has a lower level of assurance, but can be used when care organisations trust each others employee enrollment process.
  • Fixed issue where VDR could no longer update broken DID Documents.
  • Added API calls to Didman to update endpoints and compound services (previously, they had to be deleted and then recreated to change them).
  • NutsAuthorizationCredentials and NutsOrganizationCredentials now require a valid credentialSubject.id (meaning it is a DID).

What's Changed

Read more

Hazelnut update (v5.2.2)

16 May 14:25
3c83b39
Compare
Choose a tag to compare

Release date: 2023-05-16

  • Fixed issue where VDR could no longer update broken DID Documents.
  • Reverted VCR API change in which credentialSubject was returned as an array instead of an object.

Full Changelog: v5.2.1...v5.2.2

Hazelnut update (v5.1.1)

16 May 07:43
d8b2b9f
Compare
Choose a tag to compare

Release date: 2023-05-16

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

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