Fix refreshing eclipse oauth2 token #1388
Merged
+10
−7
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
…ility with keycloak
autumnfound
approved these changes
Nov 17, 2025
Contributor
autumnfound
left a comment
autumnfound
left a comment
There was a problem hiding this comment.
LGTM. This now follows the Keycloak standard way of exchanging tokens: https://www.keycloak.org/securing-apps/token-exchange
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.
This fixes #1387 .
Since the Eclipse oauth provider has switched to keycloak, refreshing an existing token did not work anymore as keycloak expects the POST parameters provided with
application/x-www-form-urlencodedinstead of json.