Allow verifying access tokens #5
Open
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
Added preinstall script to build correctly when installing from git
Fix typo
Added npx to compile so it can build when necessary
Added typescript version to npx
Added other types dependencies to compile script
Removed script modifications
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.
Previously the verification was hard coded to support only id as token_use. I opened it up to allow an input parameter from the validator's constructor to allow access token or any other potential types as well.
I also had to disable checking for aud if it is not an id since access tokens do not come with an aud
Potentially breaking change if users use fakeAuth explicitly.