Fix jwt authorizers payload v2 #1109
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @NicolasSeiler, will ship with the next version! |
This was referenced May 22, 2021
Open
This was referenced Jun 23, 2021
1 task
This was referenced Jul 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes the JWT authorizer payload for the payload v2. It also removes the
principalIdfield from the payload, since this doesn't seem to exist on the v2 payload. (Please correct me if this is wrong.)Motivation and Context
Previously, the claims and scopes were nested according to the v1 format, which breaks functions that expect the v2 payload.
How Has This Been Tested?
This was tested manually on my machine using a JWT authorizer with an AWS Cognito User Pool as the issuer and a TS function.