Skip to content

Hazelnut update (v5.3.0)

Compare
Choose a tag to compare
@reinkrul reinkrul released this 06 Jun 11:21
· 3 commits to V5.3 since this release
4db689b
  • 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

Full Changelog: v5.2.0...v5.3.0