litestar-org/litestar

Enhancement: Revoke jwt token

Open

#2,118 opened on Aug 4, 2023

View on GitHub
 (1 comment) (3 reactions) (0 assignees)Python (8,243 stars) (550 forks)user submission
EnhancementGood First IssueHelp Wanted :sos:Security

Description

Summary

Provide a mechanism to revoke a jwt token on /logout similar to flask-jwt-extended (https://flask-jwt-extended.readthedocs.io/en/stable/blocklist_and_token_revoking.html).

Basic Example

No response

Drawbacks and Impact

No response

Unresolved questions

No response

Contributor guide

Tech stack
python
Domain
backendsecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JWT knowledgeLitestar auth system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests a JWT revocation mechanism on /logout. Investigate the existing authentication module in Litestar (likely in `litestar/contrib/jwt` or similar) and consider implementing a blocklist approach similar to flask jwt extended. Since the maintainers have not clarified the preferred storage backend, start with an in memory or Redis based blocklist. Review the linked documentation for flask jwt extended for design patterns.