Location of request_object_signing_alg_values_supported Wallet Metadata parameter
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
Section 5.10 is confusing when describing the usage of the request_object_signing_alg_values_supported parameter. This chapter uses the parameter term for both Request URI parameters (namely wallet_metadata and wallet_nonce) and Wallet Metadata parameters ("the Wallet […] SHOULD use the jwks parameter within the wallet_metadata parameter…"). The paragraph about request_object_signing_alg_values_supported says "the Wallet SHOULD list […] algorithms […] through the request_object_signing_alg_values_supported parameter". It is difficult to tell if this parameter is a Request URI parameter or a Wallet Metadata parameter.
Also:
- Section 10, despite defining the Wallet metadata parameters for OID4VP, does not list
request_object_signing_alg_values_supported(norjwsalso described in 5.10). request_object_signing_alg_values_supportedis defined in OpenID Connect Discovery 1.0, but this specification is not referenced by OID4VP.- The example in Section 13.1.2 shows
request_object_signing_alg_values_supportedas a parameter inside Wallet metadata, along with parameters defined both in OID4VP and RFC 8414.
It seems that request_object_signing_alg_values_supported was intended as a Wallet metadata parameter, but confusion remains possible. Could someone please confirm this position?
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
Review Sections 5.10, 10, and 13.1.2, comparing the parameter descriptions and example with the referenced OpenID Connect Discovery 1.0 and RFC 8414 material. Clarify whether request_object_signing_alg_values_supported and jws are Wallet Metadata parameters, then make the terminology, metadata list, references, and example consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100