Error codes for HTTP Message Signatures-related errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- api, authentication, security
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.
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
- Dominant language
- HTML
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from openid/fapi
-
component: FAPI 1: Advanced migrated-from-bitbucket priority: major type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
migrated-from-bitbucket priority: trivial type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
detecting inconsistent .well-known/openid-configuration vs .well-known/oauth-authorization-server on conformance testsPossibly taken @jogu claimed this 4 days ago. Opencomponent: Certification component: FAPI2: Advanced Authorization
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
component: Certification component: FAPI2: Security Profile
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
agent-reported area/server bug good first issue hacktoberfest help wanted P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kotope/aio_energy_management#196 · 2 comments ·
-
v1 v2
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
modelcontextprotocol/python-sdk#3589 ·
Maintainers usually reply within 1 day