Question

我构建了一个带有flask-restful和flask-jwt-extended的api，并正确配置了令牌过期和失效的验证通道。但是，即使它已建立令牌过期和无效的验证回调，但api仍无法正确处理并报告错误：签名已过期

在云中的服务器上，我们有一个Centos 7 x64 16gb ram，使用19.9.0版中的gunicorn运行该应用程序。使用miniconda创建应用程序的python环境。

在生产环境中的测试中，应用程序抱怨令牌已过期。但是，在测试环境中，使用具有16 gb ram的Ubuntu 18.04.2，x64，以及与miniconda和gunicorn相同的设置，应用程序执行它就不会遇到问题，当令牌过期时会返回正确的消息。

我的jwt.py

from flask import Blueprint, Response, json, request
from flask_jwt_extended import (JWTManager, create_access_token,
                                create_refresh_token, get_jwt_identity,
                                jwt_required)

from app.models.core import User

from .schemas import UserSchema
from .utils import send_reponse, user_roles


def configure_jwt(app):
    JWT = JWTManager(app)

    @JWT.expired_token_loader
    def my_expired_token_callback(expired_token):
        return Response(
            response=json.dumps({
                "message": "Expired token"
            }),
            status=401,
            mimetype='application/json'
        )

    @JWT.invalid_token_loader
    def my_invalid_token_callback(invalid_token):
        return Response(
            response=json.dumps({
                "message": "Invalid token"
            }),
            status=422,
            mimetype='application/json'
        )

错误日志：

[2019-05-23 15:42:02 -0300] [3745] [ERROR] Exception on /api/company [POST]
Traceback (most recent call last):
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_restful/__init__.py", line 458, in wrapper
    resp = resource(*args, **kwargs)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask/views.py", line 88, in view
    return self.dispatch_request(*args, **kwargs)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_restful/__init__.py", line 573, in dispatch_request
    resp = meth(*args, **kwargs)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_jwt_extended/view_decorators.py", line 102, in wrapper
    verify_jwt_in_request()
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_jwt_extended/view_decorators.py", line 31, in verify_jwt_in_request
    jwt_data = _decode_jwt_from_request(request_type='access')
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_jwt_extended/view_decorators.py", line 266, in _decode_jwt_from_request
    decoded_token = decode_token(encoded_token, csrf_token)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_jwt_extended/utils.py", line 107, in decode_token
    allow_expired=allow_expired
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/flask_jwt_extended/tokens.py", line 138, in decode_jwt
    leeway=leeway, options=options)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/jwt/api_jwt.py", line 104, in decode
    self._validate_claims(payload, merged_options, **kwargs)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/jwt/api_jwt.py", line 134, in _validate_claims
    self._validate_exp(payload, now, leeway)
  File "/home/company/miniconda3/envs/api_ms/lib/python3.6/site-packages/jwt/api_jwt.py", line 175, in _validate_exp
    raise ExpiredSignatureError('Signature has expired')
jwt.exceptions.ExpiredSignatureError: Signature has expired

我试图理解为什么应用程序能够在测试环境中正确返回令牌到期消息，而在生产环境中它返回错误代码500 Internal Server Error。除了在我们的应用程序中解决此问题之外。

Answer 1

基于项目存储库中的此链接，我发现问题与名为True的烧瓶配置选项有关，该选项必须为async asyncData({ params }) { try { const post = await axios.get( `https://jsonplaceholder.typicode.com/posts/${params.id}` ) return { post: post.data } } catch (err) { error({ statusCode: 404, message: 'Post not found' }) } }。

flask-jwt扩展存储库中的issue帮助我找到了答案。

Answer 2

This comment指出Flask Restful需要忽略JWT和JWT Extended 例外，并提供一个简单的代码片段来解决该问题。

从上面的链接复制代码，

from flask_jwt_extended.exceptions import JWTExtendedException
from jwt.exceptions import PyJWTError

class FixedApi(Api):
  def error_router(self, original_handler, e):
    if not isinstance(e, PyJWTError) and not isinstance(e, JWTExtendedException) and self._has_fr_route():
      try:
        return self.handle_error(e)
      except Exception:
        pass  # Fall through to original handler
    return original_handler(e)

带有flask-jwt的api扩展了身份验证问题？

2 个答案: