Recommend the browser API over traditional OID4VP?
Open
Nobody has claimed this yet.
non-breaking
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
As per Lee's comment we might want to go as far as saying the Browser API (where available) is preferred/recommended.
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
Start with Lee's comment in pull request 359 and review the discussion on this issue. Determine whether the specification should recommend the Browser API where available instead of the traditional OID4VP flow; done means the scope and normative wording have consensus.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100