Skip to content

Releases: vimalloc/flask-jwt-extended

4.0.1

13 Feb 20:31
Compare
Choose a tag to compare
  • No changes from 4.0.0, this release is purely to fix some github actions and documentation builds

4.0.0

13 Feb 20:17
Compare
Choose a tag to compare

This release contains many months of work and lots of breaking changes. For full details, please see: https://flask-jwt-extended.readthedocs.io/en/stable/v4_upgrade_guide/

3.25.1

13 Feb 19:49
Compare
Choose a tag to compare
  • The only change it this release is that we are setting the metadata that marks this as the last release to support python versions earlier then 3.6 (including python 2).

3.25.0

09 Nov 22:03
Compare
Choose a tag to compare
  • Add JWT_ENCODE_ISSUER option
  • Require PyJWT before version 2.0.0a to prevent breaking changes. (we will update to the 2.0.0 pyjwt release once it's out of the alpha/early release).

3.24.1

24 Oct 15:58
Compare
Choose a tag to compare
  • Fixes a bug where missing JWTs were not being handled gracefully, introduced in version 3.23.0 (#282)

3.24.0

04 Oct 14:53
Compare
Choose a tag to compare
  • Adds the ability to add custom data to the JWT headers via the headers kwarg when making new tokens or via the jwt_manager.additional_headers_loader decorator. These headers can be accessed in your endpoints via the get_raw_jwt_header function. Thanks @iamajay for this feature! (#271)

3.23.0

10 Sep 21:22
Compare
Choose a tag to compare
  • Make header reading compliant with RFC7230, section 3.2.2 (#270). Thanks @Croug!

3.22.0

28 Aug 16:22
Compare
Choose a tag to compare
  • Adds ability to check CSRF double submit token from form data instead of headers (#269). Thanks @colevscode!

3.21.0

03 Aug 15:44
Compare
Choose a tag to compare
  • Require flask 1.0 or greater (#263)
  • Move docs to pallets-sphinx-themes (#261)
  • Add a new JWT_DECODE_ISSUER option for use with other JWT providers (#259)
  • Gracefully handle errors for malformed tokens (#246)

3.20.0

03 Jul 15:25
Compare
Choose a tag to compare
  • Look for JWTs in the same order that they are defined in JWT_TOKEN_LOCATION. Thanks @stephendwolff!(#256)