Use UserSessionUtil.findValidSessionForAccessToken in revocation endpoint #43245
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
…oint Closes keycloak#43218 Signed-off-by: rmartinc <[email protected]>
graziang
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Closes #43218
The token revocation endpoint failed for transient tokens created by the TE. The reason is the same than in previous #42565, the session can be a transient online session in which the
sidclaim is present but the client session is transient and does not exist. The PR just re-uses theUserSessionUtil.findValidSessionForAccessTokenused in other endpoints (user-info or introspection) to retrieve the session and the user. Test added.