1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
There is no issue with the authorizer. It works fine. I just want to find a way to manipulate the unauthorized response body