Added legacy transformation, currently no tests for new JWT structure #348
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.
T1 tokens are being marked as legacy to increase security. Instead, SHA256 encoded JWTs will be used by default.
Description
generateToken() now takes a default parameter that is set to true unless specifically set by the user. To use the old T1 tokens for backwards compatibility, set the parameters like so:
Motivation and Context
Increased security
How Has This Been Tested?
Tests coming for the new tokens when exact setup of claims has been identified.
Example Output or Screenshots (if appropriate):
Types of changes
Checklist: