Retrieving all client metadata from client_metadata parameter seems too restrictive
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
We have this text under several of the client id schemes, e.g. x509_hash:
"All Verifier metadata other than the public key MUST be obtained from the client_metadata parameter."
I'm not 100% sure what we intended here to be honest (given we define a very limited set of things to be valid inside client_metadata parameter), but I think we need to tweak this to be clear that it's okay to get a client name from the x509 certificate, and HAIP explicitly suggests other things like (e.g.) valid response_uri values could come from the x509 certificate.
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 the x509_hash and other client ID scheme text, along with the definition of the client_metadata parameter. Compare the current restriction with the HAIP guidance on certificate-derived client names and response_uri values, then revise the wording so the permitted metadata sources are clear.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100