DiptoChakrabarty / DiptoChakrabarty/FlaskKube-api
use jwt-extended
Open
enhancement
flask
good first issue
hacktoberfest
- Dominant language
- Python
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently jwt access tokens are used to authenticate the users using flask-jwt.
Replace it with flask-jwt-extended to provide functionality for access and refresh tokens in the given routes .
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Flask authentication routes that currently use flask-jwt and review how access tokens are issued. Compare the existing flow with flask-jwt-extended's access and refresh token behavior. Done means the affected routes use the replacement library and support both access and refresh tokens while preserving the existing CRUD behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100