feat: Add support for context and multiple identity sources #1642
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
This PR adds support for request authorizers to handle context based identity sources. But seeing as context is set by us, I am not throwing an error if context required is not set.
Also added support for request authorizers to handle multiple identity sources, all of them are now check and required for the authorization function to be called.
Motivation and Context
Following on from #1610, my personal project requires a request authorizer which use a context identity source along with a header identity source. AWS supports this by defining the identity sources as a list of comma separated strings
XXX, YYY, ZZZ
.How Has This Been Tested?
Ran locally with my Serverless Project which has a request authorizer which requires context and header identity sources.
Added some integration tests for checking the new
mixed
case.Screenshots (if appropriate):