You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tharun-d
Does this actually prevent the context from being propagated and used in template mapping on the API Gateway side?
My team and I have hit a snag where we cannot seem to be able to get the context values on the authorizer response to propagate and wonder if this is wahy.
Hi @weaverjess it's been more than 5 months, I totally forget about this,
yeah might be you cant the response values if you send other than string try only string and check whether you receive the response in string
Hi Team,
APIGatewayCustomAuthorizerResponse has some thing called
Context map[string]interface{}
json:"context,omitempty"
but atually it should be map[string]string only strings are accepted,
More documentation: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-lambda-authorizer-output.html
so it will not create any confusion if we change this to string,
If not I tried to send some json model which throws errors
Even the example is wrong:
https://github.com/aws/aws-lambda-go/blob/main/events/README_ApiGatewayCustomAuthorizer.md,
we cant send boolean or numbers also
The text was updated successfully, but these errors were encountered: