Response mode parameter values
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
The existing parameter response_mode only references that it is defined in RFC 6749, yet this parameter tells the wallet where/how to send the vp_token back to the verifier. This is especially not very clear in section "5.2 Existing Parameters", where only 'direct_post' is mentioned, without leaving syntactic room for other options (such as specified in Appendix "A.2. Request": dc_api). A clarification on the scope and role of this parameter might well be clarifying in this context.
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 section "5.2 Existing Parameters" and Appendix "A.2. Request", comparing the description of response_mode with the mentioned direct_post and dc_api values. Clarify the parameter's scope and role, including how it relates to returning the vp_token, and ensure the specification leaves room for the applicable options.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100