Skip to content

Releases: hzlmn/aiohttp-jwt

v0.6.1

07 May 18:09
914d062

Choose a tag to compare

  • Minor fix for middleware initialization check inside decorators.

v0.6.0

16 Apr 13:04
0106b6a

Choose a tag to compare

v0.5.0

23 Nov 21:02
ba9f8c1

Choose a tag to compare

Switched to new style aiohttp middleware #94 . Thanks @Ranc58

v0.4.0

25 Feb 14:56
9a58325

Choose a tag to compare

Added issue and audience claims support #80 . Thanks @idegree

v0.3.0

13 Feb 13:48

Choose a tag to compare

  • Added auth_scheme option to middleware, that allows customization of authorization header prefix. By default value is Bearer. #77 Thanks @gbarbaten

  • Added explicit exception when decorators are used without proper middleware initialization & minor cleaning #85

v0.2.0

24 Oct 17:56

Choose a tag to compare

v0.1.1

04 Apr 11:07

Choose a tag to compare

v0.1.0

28 Mar 09:02

Choose a tag to compare

  • Added support for checking revoked tokens

    Now users can pass is_revoked callback that should return bool value that indicates token status and in case of True, middleware will raise HTTPForbidden with Token is revoked message.

  • Better description for token decoding error.

  • Added more usage examples. Thanks @vikitikitavi

v0.0.2

17 Mar 14:23

Choose a tag to compare

  • Refactored handling of broken provided token.

  • Revisited naming of certain properties and helpers.

    • ONE_OF to match_any
    • ALL_IN to match_all
    • strategy to comparison
  • Improved overall code test coverage.

Initial release

15 Mar 12:53

Choose a tag to compare

  • Introduced check_permissions decorator for providing scope based permission model for your application handlers.

    Permissions should be described as an array of strings inside the JWT token, or as a space-delimited OAuth 2.0 Access Token Scope string.

  • Introduced JWT middleware for encoding/verifying your JWT token and setting property on aiohttp.Request object.