Error codes for HTTP Message Signatures-related errors
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by Takahiko Kawasaki (Takahiko Kawasaki) on 2024-09-30
It may be worth considering defining new error codes for HTTP message signature verification errors.
RFC 9449 OAuth 2.0 Demonstrating Proof of Possession (DPoP) has defined invalid_dpop_proof and use_dpop_nonce error codes for DPoP-related errors. Similarly, OAuth-aware applications using HTTP Message Signatures may want dedicated error codes for HTTP Message Signatures-related errors. For example, invalid_http_message_signature.
Without such dedicated error codes, the userinfo endpoint implementation I’m working on will eventually return invalid_request for HTTP message signature verification errors, as there doesn’t seem to be any more appropriate error code among the currently available ones.
Bitbucket status: open
Bitbucket origin: issue 719
Contributor guide
No contributing guide indexed for this repository
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 by reading the linked RFC 9449 error-code definitions and the existing error codes referenced in the issue. Review how HTTP Message Signature verification errors are currently represented, especially for the userinfo endpoint. Done means reaching and documenting a decision on whether dedicated codes such as invalid_http_message_signature or use_dpop_nonce are appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100