Add support for empty identity sources on request authorisers.
Motivation and Context
If you have a custom authoriser that supports checking multiple identity sources, you need to override the default identity source provided by AWS such that AWS does not validate any identity sources before calling the lambda authoriser. This is because AWS validates that all identity sources are present before calling the lambda authoriser, and since one of more of the identity sources may not be present this becomes an issue.
This used to work in version 11.3.0 but has been broken since.
How Has This Been Tested?
This has been tested locally to ensure that when a identity source of '' has been specified the custom authoriser is still run and is able to deny or approve the request.
Description
Add support for empty identity sources on request authorisers.
Motivation and Context
If you have a custom authoriser that supports checking multiple identity sources, you need to override the default identity source provided by AWS such that AWS does not validate any identity sources before calling the lambda authoriser. This is because AWS validates that all identity sources are present before calling the lambda authoriser, and since one of more of the identity sources may not be present this becomes an issue.
This used to work in version
11.3.0but has been broken since.How Has This Been Tested?
This has been tested locally to ensure that when a identity source of
''has been specified the custom authoriser is still run and is able to deny or approve the request.Screenshots (if appropriate):