1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
Assuming you are using the HTTP API with a JWT Authorizer, that should not be an issue. Please take a look at this document - https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-jwt-authorizer.html
If you look at this section
Authorizing API requests API Gateway uses the following general workflow to authorize requests to routes that are configured to use a JWT authorizer.
Check the identitySource for a token. The identitySource can include only the token, or the token prefixed with Bearer .
So adding the token pre-fixed with Bearer is acceptable. The problem could be somewhere else.
Contenus pertinents
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans