jaredhanson / jaredhanson/oauth2orize
[Decision/Grant] ForbiddenError: Unable to load OAuth 2.0 transactions
- Dominant language
- JavaScript
- Stars
- 3.5k
- Forks
- 472
- PR merge metrics
- No merged PRs in 30d
Description
When I stayed at approval dialog, I tried to duplicate the dialog. In the first one, I chose Deny and it was fine. But in the second one, When I clicked to Deny, I got this message 'ForbiddenError: Unable to load OAuth 2.0 transactions: ...' and It made my server crashed. I knew that because the transaction_id was not available anymore but my question is How can I handle any error of oauth2orize to don't let the server be crashed.
Contributor guide
Research direction
Reproduce the duplicate approval-dialog flow described in the issue, especially denying the second dialog after the transaction_id is unavailable. Trace how oauth2orize handles that failure and verify that denying an invalid or expired transaction no longer crashes the server and is handled as an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript, node.js
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100