vimalloc / vimalloc/flask-jwt-extended
Implicit Refreshing With Cookies example has a bug
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 253
- PR merge metrics
- No merged PRs in 30d
Description
There is a possible conflict between logout and token prolongation. In the actual example, a new access cookie could be set after the logout request.
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
Inspect the “Implicit Refreshing With Cookies” example and trace how logout interacts with token prolongation. Reproduce the case where an access cookie is set after logout; done means the example no longer allows a new access cookie to be set after the logout request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100