Flask JWT Extended
Flask-JWT-Extended not only adds support for using JSON Web Tokens (JWT) to Flask for protecting views, but also many helpful (and optional) features built in to make working with JSON Web Tokens easier. These include:
- Support for adding custom claims to JSON Web Tokens
- Custom claims validation on received tokens
- Creating tokens from complex objects or complex object from received tokens
- Refresh tokens
- Token freshness and separate view decorators to only allow fresh tokens
- Token revoking/blacklisting
- Storing tokens in cookies and CSRF protection
- Developed at devel:languages:python:flask
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/python-flask-jwt-extended && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| Flask-JWT-Extended-4.5.2.tar.gz | 0000034227 33.4 KB | |
| python-flask-jwt-extended.changes | 0000004090 3.99 KB | |
| python-flask-jwt-extended.spec | 0000002665 2.6 KB |
Revision 3 (latest revision is 4)
Dominique Leuenberger (dimstar_suse)
accepted
request 1093727
from
Steve Kowalik (StevenK)
(revision 3)
- Update to 4.5.2:
* Updated typing of expires_delta and fresh by @eMaerthin in #510
* Allow selective disabling of blocklist check by @indrajeet307 in #501
* Fix compatibility with flask version 2.3 (#493)
* Drop support for python 3.6
* Add option to include current_user in jinja templates by default (#478)
* Fix mypy type checks for current_user (#488)
* Fix mypy explicitly mark exported names #484
* Fix verify_type being set to False by default in
verify_jwt_in_request() #483
* Fix PEP 561 compatibility #480
* Drop support for Flask 1
* Add verify_type argument to view decorators to allow accepting both
refresh & access tokens #460
* Relax dependency pinning for cryptography package (#467)
Comments 0