Repository navigation
Practical viability & stability of external-2-internal token-exchange #39921
Unanswered
Patrik-Stas
asked this question in
Q&A
Replies: 1 comment 1 reply
|
Yes, the plan is to make support for other token exchange use-cases besides internal-internal. We want to support external-to-internal officially (as current support with V1 is only a preview support). This may happen in Keycloak 26.4, but no hard promise... It is possible that current "Legacy token exchange" will be removed one day, but no without replacement of the most important use-cases, which are currently supported by it (And external-to-internal is the most widely used use-case besides internal-internal, which is already supported by token-exchange-standard:V2). |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi team/community,
while I am aware of V1 token-exchange being called "legacy" I am confused about it's actual support in the future. I would like to ask you some additional feedback on the state of it / future plans. I observe various conflicting signals:
Do not use signals:
Use signals:
I understand you may not want to make false promises, so it's safer to say only V2 is supported and I take it in account in decision making. Still, can you add some additional commentary on using V1 for stuff like external-2-internal token-exchange? Is this something that may be simply disabled one day? Or is it more likely to be deprecated in phases with some V2 alternative to switch to?
Thank you very much!
All reactions