jaredhanson / jaredhanson/oauth2orize
Transaction id in req.session.authorize and cookie Session
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.5k
- Forks
- 472
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I am using node-client-sessions library to store sesison in cookies.
in the /dialog/authorize endpoint whenever I load the page it seems to be setting new transaction id in authorize key of req.session. so if i refresh the page say for about 5-6 times it seems to be increasing the size of cookie and eventually it will be more than allowed cookie size of 4095 bytes. Is it not recommended to use cookie session with this library?
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
Start at the /dialog/authorize entry point and inspect req.session.authorize while reproducing repeated refreshes with node-client-sessions; compare cookie size after each load against the 4095-byte limit. Done means a maintainer-confirmed explanation of whether cookie sessions are supported here and a clearly identified change or documentation need.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100