Handle large SDT values with SHA256 in JWT tokens #1157
Conversation
This file contains hidden or 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
…ed SDT exceeds a predefined size limit, its SHA256 hash is stored in the token instead of the full value. This ensures token size remains manageable while maintaining data integrity for verification
claudiamurialdo
had a problem deploying
to
kafka-integration-tests
GitHub Actions
Failure
claudiamurialdo
had a problem deploying
to
external-storage-tests
GitHub Actions
Failure
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.
Added logic to handle large SDT values in JWT tokens. If the serialized SDT exceeds a predefined size limit, its SHA256 hash is stored in the token instead of the full value. This ensures token size remains manageable while maintaining data integrity for verification
Issue:204823