1 個回答
- 最新
- 最多得票
- 最多評論
0
Have a look at this: https://repost.aws/knowledge-center/api-gateway-401-error-lambda-authorizer, as it could be issues with configuration or usage/lack of tokens.
Also double check whether you resource policy may have a role into this.
相關內容
- AWS 官方已更新 2 年前
There is no issue with the authorizer. It works fine. I just want to find a way to manipulate the unauthorized response body