Provide more token storage options
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 40
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In certain threading and hosting situations, the in-memory token store isn't super reliable, causing intermittent difficulties for login (especially via email). It's time to finally provide some key-value backing storage as described in the docs.
Possibilities:
- SQLite (file-backed)
- redis
- memcached
- lmdb
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
Start with the token-storage section of the linked Authl documentation and inspect how the current in-memory token store is used. Determine which key-value backend or backends should be supported, then consider the work complete when persistent storage options are implemented and documented for the login flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- memcached, python, redis, sqlite
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100