nuts-foundation / nuts-foundation/nuts-node
replace client_metadata_uri with client_metadata parameter in OpenID4VP flow
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
The next version of the OpenDI4VP spec deprecates the client_metadata_uri in favor of directly adding the client_metadata to the authorization request.
We should probably also replace the presentation_definition_uri with presentation_definition. This way a wallet only needs to make 1 API call to collect the request object (JAR) that contains all relevant info for the request
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Go code that parses OpenID4VP authorization requests and handles client_metadata_uri and presentation_definition_uri. Trace the request-object flow and its tests before deciding how direct client_metadata and presentation_definition values should be accepted. Done means the flow supports the new parameters and can obtain all relevant request data in one API call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100