Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OIDC4VCI: Write RFC #258

Open
reinkrul opened this issue Apr 10, 2023 · 0 comments
Open

OIDC4VCI: Write RFC #258

reinkrul opened this issue Apr 10, 2023 · 0 comments

Comments

@reinkrul
Copy link
Member

reinkrul commented Apr 10, 2023

The OIDC4VCI spec is really flexible, but we don't need everything. Thus, to reduce complexity, we should specify what we actually use.

Part of the Nuts RFC on the topic.

Specify:

  • which grants are supported (pre-authorized code)
  • how wallet metadata is discovered (registration of oidc4vci-wallet-metadata URL in DID document)

Could use a description of example use cases:

  • Phase 1: Issuer initiated credential issuance of NutsAuthorizationCredential (e.g. initiating eOverdracht transfer)
  • Phase 2: Requesting credential issuance of Nuts AuthorizationCredential (e.g. care professional requesting access to patient dossier at other care organization)
  • Phase X: Receiving care organization credential (e.g. issued by LrZA)
  • Phase X: Issuing and receiving any other credential (e.g. KIK-v)

Also determine and specify:

  • which certificate(s) are to be used (PKIoverheid Private Services or a publicly trusted one).
  • what is contained in the challenge, which is signed as c_nonce
  • do we support multiple credential subjects? (would require offering to multiple wallets)
@reinkrul reinkrul transferred this issue from nuts-foundation/nuts-node Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant