Fixing JWT expiration extraction - #692
Open
Myllyenko wants to merge 1 commit into
Open
Conversation
JWT parts are base64url encoded (RFC 7515), but extractExpireAt used Base64.getDecoder(), which rejects '-' and '_' with IllegalArgumentException. Any token whose payload happened to contain those characters failed to parse, so the caller fell back to the default value. Also stop logging the jwt itself on a parse failure - it is a bearer credential and does not belong in the logs.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #692 +/- ##
============================================
+ Coverage 71.91% 71.96% +0.04%
Complexity 3474 3474
============================================
Files 390 390
Lines 16220 16220
Branches 1698 1698
============================================
+ Hits 11664 11672 +8
+ Misses 3904 3898 -6
+ Partials 652 650 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
1 participant
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.
JWT parts are
base64urlencoded (RFC 7515), butextractExpireAtusedBase64.getDecoder(), which rejects-and_withIllegalArgumentException. Any token whose payload happened to contain those characters failed to parse, so the caller fell back to the default value.Also stop logging the jwt itself on a parse failure - it is a bearer credential and does not belong in the logs.