feat: update scope cookie to accurately reflect user scopes in access… #102
+31
−15
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
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.
… token
Issue #101
Description of changes:
Updates the tokenScopesString cookie value to accurately reflect the scopes in the user's access token. The access token is verified and parsed using the _jwtVerifier. To achieve this, tokenUse was moved from the constructor to the verify calls. I've forked the repository and deployed the changes to a running Lambda@Edge, confirming that everything works as expected. Tests have been updated accordingly.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.