python-jose VS flask-jwt-extended

Everything that's in `/app` is the compiled application; changes should be made locally and redeployed. Looking at the `python-jose` package, they've made the changes already (https://github.com/mpdavis/python-jose/blob/master/jose/jwt.py) so should be able to update `python-jose` locally (`requirements.txt`, I think?) and re-deploy to solve this.

I use JOSE for the JWT token creation https://github.com/mpdavis/python-jose

If you're using a API Gateway REST API, then yeah, a lambda authorizer is the way to go. You can use something like python-jose to work with the JWTs.

flask-jwt-extended, Flask extension that provides JSON Web Tokens (JWT) support;

After the maintainer of flask-jwt stopped updating his package, flask-jwt-extended was started as a new project. The author originally wanted to extend flask-jwt but instead had to create a new project. Like flask-jwt, flask-jwt-extended is opinionated, but takes things to the next level. The flask-jwt-exetended extension is very full featured and eminently configurable. It is an excellent package with a lot of activity and support.

The error you're seeing is coming from the PyJWT library, from this line, I think. jwt.encode(..) returns a string, which does not have a .decode(..) attribute/method.