This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
feat: allow regex in SMARTConfig.expectedAudValue #43
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Allow RegExp as expectedAudValue.
This enables use cases where the apiUrl is not static. The main use case is for multi-tenancy with tenant-specific urls, but there may be other use cases.
Only minor code changes are required since the
jsonwebtokenpackage already acceptsstring | RegExpwhen verifying the aud value.https://www.npmjs.com/package/jsonwebtoken#jwtverifytoken-secretorpublickey-options-callback
Note: This is intended to support multi-tenancy but it is a generic change so no feature branch is being created.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.