Repository navigation
Check current token state after verified JWT admission - #48
Merged
Merged
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
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.
An unexpired locally verified JWT can outlive the current provider account or session state. Add an explicit LIVE admission mode that performs an uncached current-state check after the existing local JWT verification, binds issuer, subject, client, audience and expiration, and preserves the original verified Jwt. Unsupported, empty, malformed, timed-out or failed checks refuse without stale/local fallback. LOCAL_JWT remains the default, and existing SPI implementations refuse the new method until they support it deliberately.
Use native Spring introspection, owned JDK HTTPS transport and bounded Jackson/Spring codecs. The managed Jackson dependency has no version override. BearerToken diagnostic rendering becomes constant redaction while retaining its published final modifier. Existing default-chain APIs remain available; custom security chains must explicitly adopt the decoder decorator. The operating guide explains configuration and deployment verification.
Validation:
No root/parent/BOM version, generated SDK, or Cache PR47 source changes. Published 26.10.23 is unchanged; this addition requires a future qualified whole-framework release.