feat: include JTI or SubId as tokenId for JWT/OIDC#45
Merged
chrisbonilla95 merged 1 commit intomasterfrom Jan 22, 2025
Merged
Conversation
Previously tokenId would only hold ID of ApiToken, but we'd also like to know the JTI for JWT or the SubId for OIDC use cases. JIRA: LX-671 risk: low
chrisbonilla95
force-pushed
the
cbon-lx-671-enhanced-tokenId
branch
from
d51cbe7 to
9b37917
Compare
jeskepetr
approved these changes
Jan 22, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 tokenId would only hold ID of ApiToken, but we'd also like to know the JTI for JWT or the SubId for OIDC use cases.
JIRA: LX-671
risk: low