Search Results

After configuring the Nuts node with the required artifacts, the use case can be activated for a subject. This means activating the related Discovery Service for the subject, making them discoverable. Pre-requisites: You have created a subject for the organiz...

The configuration below show a minimal nuts.json config file: did:nuts disabled, did:web enabled discovery refresh of 1 minute for faster discovery during development default mappings for discovery and policy files (mounts required) SQLite will be used as DB...

The first thing you need to do is create some public/private key material for your subjects. We use the term subjects for everything related to vendors, tenants, organizations and clients. Behind every subject there can be multiple DIDs (decentralized identifi...

After you created a subject with some DID documents, it's time to give meaning to these identifiers. Without Verifiable Credentials, DIDs are just useless identifiers. They receive meaning when another party issues credentials to one of those DIDs. Attestation...

Before another party can interact with you, they will first need to find your endpoints. The discovery service in the Nuts node can help you. The Nuts node can act as both server and client. From a use case definition you'll receive the following information/f...

You can find participants of a use case via their registered services. A use case defines the service identifier and which credentials are required through the presentation definition. Any constraint in the presentation definition with an identifier can also b...

After finding a service endpoint to interact with, it's time to request an access token. You can request one via your own Nuts node: POST /internal/auth/v2/my_subject_identifier/request-service-access-token { "authorization_server": "https://example.com/oau...

When a request comes in at your resource endpoint, an access token should be available in the HTTP Authorization header. You can validate the token by calling: POST /internal/auth/v2/accesstoken/introspect token=ciOiJSUzI1NiIsInR5cCI6Ikp Note: the content-ty...

Abstract This proposal describes a method for issuing Verifiable Credentials by leveraging the existing chains of trust provided by X.509 certificates. For this it uses the did:x509 did-method. Status of this document This document has the status draft. Introd...

Google doc

When updating your node from V5 to V6, you can choose to disable/enable certain parts depending on your needs. The common paragraph describes the required configuration changes. Common Before you update, make a backup and check the diagnostics of your node. To...

It's possible to downgrade an v6.0.0 node back to v5.4.x. You'll also need to reset your configuration. The SQL database you configured for V6 can be removed. DID documents are still changed after the downgrade with the controller field removed.

When you upgrade from V5 to V6, your DID documents will be migrated to a SQL database. A new VDR V2 API has also been added. It's no longer possible to set a controller on a DID document. All DID Documents are self-controlled. It's also no longer possible to f...

Together with V6 comes a new understanding of how data exchange should be secured across organization boundaries. Some of the concept, promoted by Nuts in the past, are no longer viable or don't make any sense anymore. V6 supports alternatives or this wiki des...

Dit document heeft de status DRAFT. De Ontwikkeling van deze specificiaties worden op de Github Respository uitgewerkt. Dit betreft v0.2 van het Zorgtoepassingsprofiel huisartsinzage in het thuiszorgdossier en bouwt voor op versie 0.1, maar maakt gebruik van d...

Hieronder volgt de uitwerking van Huisartsinzage (plateau 1: Huisarts inzicht geven in het VVT dossier) aan de kant van het doelsysteem (huisarts). In het geval van Topicus is dit als volgt: *Let op: dit zijn schermontwerpen, de daadwerkelijke software impleme...

Samenwerking Slack kanaal Functionele beschrijving omnichannel chat Technische doccumentatie OZO chat via FHIR. Scope Het faciliteren van organisatieoverstijgende ongestructureerde communicatie. Functionle eisen zijn opgesteld in een document. Veel appl...