Allow wallets to proceed with signed requests when the signature verification fails/can't be performed but the user wants to proceed anyway?
Open
Nobody has claimed this yet.
discuss if we do this
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
As per Martijn's comment https://github.com/openid/OpenID4VP/pull/356#issuecomment-2511923596 - namely:
Shouldn't we also extend this to scenarios where the wallet does not verify the signature but still decides to continue, e.g. because it cannot, because it doesn't want to or another reason.
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 Martijn's comment on pull request 356 and the three comments on this issue. No files, tests, or entry points are named; clarify the expected behavior when a wallet cannot or chooses not to verify a signature, then identify the relevant OpenID4VP specification section and define interoperability and security requirements before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100