use of redirect_uri prefix unclear
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
The specification is unclear about what to do when redirect_uri parameter (or response_uri for that matter) and the Client Identifier Prefix redirect_uri are both present and do not match.
Section 8.2 states that response_uri or redirect_uri parameter when present MUST be used. Therefore section 5.9.3 should note under redirect_uri that the parameter if present takes priority or mention that an error response (which?) is to be sent.
Contributor guide
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
Read sections 8.2 and 5.9.3 of the OpenID4VP specification, focusing on the interaction between the redirect_uri or response_uri parameter and the Client Identifier Prefix redirect_uri. Clarify which value takes priority or specify the required error response when they do not match; the specification is done when this case has one unambiguous outcome.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100