pebble-dev / pebble-dev/rebble-auth-py
Technical Debt: Consider migration to Authlib
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Description
Currently, we're using Flask-Oauthlib, which works, however it depends on a whole bunch of packages we also depend on. This normally wouldn't be an issue, but Flask-Oauthlib is deprecated and forcing us to use many older dependencies (for instance, the highest Werkzeug version we're allowed to use is 2.3.8, as Flask-Oauthlib uses some 2.x-only features. This also means the latest version of Flask we can use is 2.3.3).
The fix for this is to upgrade to Authlib, which is maintained and is the spiritual successor to Flask-Oauthlib as indicated by it's README.
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
The issue does not name files, tests, or entry points. Start by locating the Flask-Oauthlib integration and its dependency constraints, then review Authlib's migration guidance. Done means the integration uses Authlib and the project can upgrade its Flask and Werkzeug dependencies without breaking authentication tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- authentication, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100