nuts-foundation / nuts-node

The reference implementation of the Nuts specification. A decentralized identity network based on the w3c ssi concepts with practical functionality for the healthcare domain.

https://nuts-foundation.gitbook.io

GNU General Public License v3.0

23 stars 15 forks source link

Demo requesting a VP from a mobile wallet #2472

Open reinkrul opened 1 year ago

reinkrul commented 1 year ago

Have the Nuts node as verifier request a VP from a mobile wallet (Sphereon Wallet for now) to have a care professional provision their identity.

[ ] Implement authz request object passing through request_uri parameter. The request object needs to be a signed JWT (see https://www.rfc-editor.org/rfc/rfc9101.txt).
[ ] Support serving did:web (https://github.com/nuts-foundation/nuts-node/pull/2433)

reinkrul commented 1 year ago

What I've deduced from SIOPv2 vs OpenID4VP spec is the following, given the response type:

id_token implies usage of SIOPv2
vp_token implies usage of OpenID4VP
id_token vp_token implies usage of OpenID4VP with the ID token definition defined in §11 from SIOPv2

Choosing a wallet to support;

Sphereon Wallet
Paradym (uses Sphereon SDK)
Trustbloc Reference Wallet

Sphereon Wallet

Supports:

SIOPv2 implementer's draft 1 (ID1), this is draft v7: https://openid.net/specs/openid-connect-self-issued-v2-1_0-ID1.html
SIOPv2 draft v11
JWT VC Presentation Profile v1
Claims to support "OIDC4VP" (how ARF calls OpenID4VP, old name for the same spec), but appears (traced through the wallet's auth request handling) only as extension to the base SIOPv2 flow.

Paradym

Not considered, as it uses the Sphereon SDK, meaning the same features as the Sphereon wallet?

Trustbloc

Needs a custom build since they don't distribute their mobile apps (you need to build them yourself), so not really scalable from demo into a POC?