nuts-node
nuts-node copied to clipboard
The reference implementation of the Nuts specification. A decentralized identity network based on the w3c ssi concepts with practical functionality for the healthcare domain.
the OpenID4VCI flow has multiple possible AuthorizationServers defined in the credential issuer metadata. This can be a different endpoint than derived from the did:web issuing the credential. We must use...
Currently we add a `nonce` to all (JAR) Request Objects. The nonce should only be present if the client/RP expects the server to incorporate it into the result, such as...
closes #3124
closes #3063 rewrote nonce validation in `handleAuthorizeResponseSubmission` since it assumed the first VP contained the "correct" nonce and later on did a second validation over all VPs
Instead of generating one in application space, and then importing it into the key storage. This allows supporting unexportable keys, meaning keys that never leave the key store. This is...
The OpenID4VP flow is meant for getting an access token for data retrieval where a user should be involved. For any medical or personal data that is retrieved the source...
In lots of OAuth2 protocol parts we need to check a nonce is used once. This is not done everywhere (yet)
It shows the data type as list of strings instead of showing it as a string and displaying multiple examples.
The oauth client and server metadata indicate what combination of parameters/operations are supported by the client/server. We often don't confirm that the other party actually supports what we are presenting....