Release notes

Whats has been changed, and how to update between versions.

v0.15.0

This release adds the p2p registry. Github is still used as backup registry but registry updates should now be instant!

Project board: https://github.com/orgs/nuts-foundation/projects/9 Required migrations: Migration

Features / improvements

Bugfixes

v0.14.0

This release added additional information to the Corda states. This allows vendor software to diagnose any problems and have a better understanding what the current state of a consent request is.

For specific issues also see: https://github.com/orgs/nuts-foundation/projects/12

Upgrading from v0.13.0

Starting version 0.14 vendors and organizations will have an X.509 certificate (encoded in the JWK) associated with their key pairs. These certificates are used to identify the holder of the key pair used to sign events, which is also introduced in this version.

Action required: This migration can be performed by the Nuts node; use the newly introduced registry verify command with the –fix flag to generate key pairs (if necessary), issue certificates and sign events. Don’t forget to publish these changes to the central registry. See 5. Verifying and fixing registry data for the command.

See Migration for a complete overview of all migrations.

Features / improvements

Bugfixes

All bugs were fixed in 0.13.x versions.

v0.13.0

Focus of this relase was on robustness; automatic resumption of listeners/handlers, no more lost events or duplicate events. Developer Happiness by providing scripts to setup the nuts-local-network. Adding a Demo-EHR so nuts becomes clickable. Improving the registry by making it event based and adding signatures. Provide a convenient API authorization method by providing an easy to use OAuth 2 flow which accepts IRMA identity tokens.

For specific issues also see: https://github.com/orgs/nuts-foundation/projects/8

Upgrading from v0.12.0

The registry now also contains vendors and since a node must be linked to a vendor, the nuts.yaml must now contain an identity. Checkout Nuts service config for the details.

See Migration for a complete overview of all migrations.

Features / improvements

Bugfixes

v0.12.0

See github project for more details

Features / improvements

  • Added status endpoint for consent-bridge available under /status
  • Added status endpoint for service executable available under /status
  • Added diagnostics endpoint for consent-bridge available under /status/diagnostics giving information about the service health. Things like connection status, disk status etc.
  • Added diagnostics endpoint for service executable available under /status/diagnostics giving information about the service health. Things like connection status, disk status etc.
  • Added docs about service monitoring
  • JWK’s are now internally used for key representation
  • Added Ping flow to Corda to check if nodes can contact each other. Available via diagnostics
  • Corda contract now also checks if old consent records are re-offered
  • When creating a session, the existence of the given legal entity is checked
  • The registry files have changed from state-based to event-based.

Bugfixes

  • The public key JWT check was broken (nuts-foundation/nuts-auth#29)
  • The return value for the consent check was wrong (nuts-foundation/nuts-consent-store#30)
  • Path variables in http service are now decoded correctly (nuts-foundation/nuts-go-core#7)
  • Fix for consent query when no validTo was given (nuts-foundation/nuts-consent-store#31)

v0.11.2

See github project for more details

Bugfixes

Upgrading from v0.11.0

Because of the corrupted dataClasses, all data has to be wiped. Both the persistence.mv for Corda and the sqlite DB for the consent store have to be deleted.

v0.11.0

See github project for more details

Features / improvements

  • A version number has been added to the FHIR consent record (FHIR consent requirements) which is also visible in the consent-store. Currently, the API’s will only return the latest version. The version is mainly for forwards compatibility and for viewing changes in consent in future releases.
  • The consent-store query API has been changed to return a PatientConsent model instead of a SimplifiedConsent model , ref: Nuts consent store API.
  • Changed consent on the level of individual FHIR resources (Patient, Observation, etc) to data classes (Medical, Social, Mental) across all modules. Mapping individual FHIR resources to and from classes is future work.
  • Public keys in registry can now be stored in JWK format. All api’s that request or return public keys can handle JWK format.
  • Period dates in the consent store have been changed to datetime objects instead of dates. This is mainly done for when consent is withdrawn, it should not be active for the rest of the day.
  • Corda has been updated to 4.3.

Bugfixes

  • Fix incorrect return values for hash and ID in the consent-store api
  • Fix usage of validAt query param on consent-store query api
  • Fix period adherence in login contract creation
  • Fix technical error when validating login contract

v0.10.0

See github project for more details

Features / improvements

  • Signed JWTs with private key of requestor. This allows the custodian to check if JWT has been created by the requestor instead of being reused from another party.
  • Add strictmode flag which forbids unsafe config options.
  • Add IRMA schememanager config flag which allows setting demo or production attributes
  • Recover events on startup
  • Purge completed events at startup
  • Add retry queues for failed events by a temporary cause
  • Make nats subscription durable
  • Updates all the modules to go 1.13, allowing for the new encapsulating errors
  • Compare public keys by object instead of by string

Bugfixes

  • Fix 500 on createConsent API call when body is incomplete / empty
  • Fix nullpointer error on incorrect legalName in cordapp