Implement the ability to define a leeway when validating JWT tokens.

[otetard]

PyJWT library implement a way to define a “leeway” for time
validations.

PyJWT also supports the leeway part of the expiration time
definition, which means you can validate a expiration time which is
in the past but not very far. For example, if you have a JWT payload
with a expiration time set to 30 seconds after creation but you know
that sometimes you will process it after 30 seconds, you can set a
leeway of 10 seconds in order to have some margin:

https://github.com/jpadilla/pyjwt/blob/master/docs/usage.rst

This is implemented as an optional configuration setting,
JWT_DECODE_LEEWAY.

[pep8speaks]

Hello @otetard! Thanks for updating the PR.

Cheers ! There are no PEP8 issues in this Pull Request. 🍻

Comment last updated on January 03, 2019 at 10:56 Hours UTC

[coveralls]

Coverage remained the same at 100.0% when pulling 7617540 on otetard:feat/implement-leeway-in-jwt into c5f32c3 on vimalloc:master.

[vimalloc]

This commit looks good, thanks for making it! I added a few minor nit picks in the code, if you don't mind taking a look at those. Could you also add that new option to the documentation here: https://github.com/vimalloc/flask-jwt-extended/blob/master/docs/options.rst

Thanks!

[otetard]

Thanks @vimalloc for your review! I’ve updated my PR to take your comments into account.

[vimalloc]

I released this in version 3.15.0, it should be showing up on pypi soon. Thanks for contributing! 👍