fix: skip adding authorizer to event if no authorizer is configured #1786
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
AWS API Gateway does not include the
event.requestContext.authorizer
field if there is noauthorizer
configured for the function.This PR deletes the
event.requestContext.authorizer
field if the function does not have an authorizer.Motivation and Context
authorizer
payload didn't match what it expectedserverless-offline
was always settingevent.requestContext.authorizer
if aBearer
token comes through in the HTTP Authorization headers.event.requestContext.authorizer
if the lambda function does not have anauthorizer
set.How Has This Been Tested?
I've written tests and included them in this PR. Please let me know if you want me to kick the tires in any other ways!