1 Answer
- Newest
- Most votes
- Most comments
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.
Relevant content
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
There is no issue with the authorizer. It works fine. I just want to find a way to manipulate the unauthorized response body