2 Answers
- Newest
- Most votes
- Most comments
1
This problem has been resolved. The answer was that the API Gateway Authorizer was utilising a token validation expression. Which validates on the aud
field within the request token.
Removal of the validation expression fixed this issue as the access_token does not have an aud
field present. Only id_tokens have that field present.
answered 4 years ago
1
This problem has been resolved. The answer was that the API Gateway Authorizer was utilising a token validation expression. Which validates on the aud
field within the request token.
Removal of the validation expression fixed this issue as the access_token does not have an aud
field present. Only id_tokens have that field present.
answered 4 years ago
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked 3 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago