1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
You can take the following steps to troubleshoot the authorizer:
- Verify token signature is disabled for the authorizer using the console or
aws iot describe-authorizer --authorizer-name NAME_OF_AUTHORIZER - If you have multiple authorizers, verify the one you want to use is set as default
- Verify the authorizer response with
aws iot test-invoke-authorizer --authorizer-name NAME_OF_AUTHORIZER --token TOKEN_VALUE - Test the lambda function using a sample event
Token and the signature can be sent as headers in the request or as query paramenters. For your case the authorizer lambda code must be written to handle query strings parameters.
A more exhaustive troubleshooting guide can be found here
Contenus pertinents
- demandé il y a un mois
- demandé il y a un an
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
Thank You so much for the response. I have done the following : 1.Added "Addpermission"API with the given command.
aws lambda add-permission --function-name FunctionName --principal iot.amazonaws.com --source-arn AuthorizerARn --statement-id Id-123 --action "lambda:InvokeFunction"
2.Verify Authorizer Response with the command aws iot test-invoke-authorizer --authorizer-name NAME_OF_AUTHORIZER --token TOKEN_VALUE
In AWS CLI gives the following error: aws: error: argument operation: Invalid choice, valid choices are:
And Postman API is still giving {message Forbidden} :( Note:Token Signature is up todate