Repository navigation
Conversation
emouty
force-pushed
the
test-internal-token-exchange-on-refresh-token
branch
2 times, most recently
from
March 30, 2026 09:09
06d289a to
08807b2
Compare
…eycloak#36683) Closes keycloak#36683 Signed-off-by: Erwan Moutymbo <emoutymbo@libon.com>
emouty
force-pushed
the
test-internal-token-exchange-on-refresh-token
branch
from
March 30, 2026 13:00
08807b2 to
d03f87a
Compare
emouty
marked this pull request as ready for review
March 30, 2026 13:00
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.
Closes #36683
This pr introduce the support of using a refresh token as a subject in a token exchange. The use case that motivated us to implement this feature is described here #26502 (comment)
To avoid introducing a behaviour change on existing Keycloak deployments, this feature is driven by a new attribute on clients
attributes.standard.token.exchange.enableRefreshSubjectTokenTypewith value asfalseby default. It can be enabled through the admin panel inClient -> Advanced -> OpenID Connect Compatibility Modesnote : I saw that there is a open PR #47516 regarding a refactoring of the standard token exchange tests. If its merged before this pr is reviewed I'll update it to comply to the new tests classes
Signed-off-by: Erwan Moutymbo emoutymbo@libon.com