Keycloak: Add Token Refresh #2601
Open
Conversation
This file contains 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
tuunit
reviewed
Apr 12, 2024
|
Ran into this while using "Keycloak OIDC", had 502 errors until I disabled "Use refresh tokens" in keycloak. |
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.
Description
The missing implementation of the token refresh for the OAuth2 provider: "Keycloak" is implemented here.
Motivation and Context
When using the OAuth2 proxy, I noticed that no token refresh is implemented for the provider: "Keycloak". In the past, this issue has already been noted in issue: #501.
This PR will fix #501.
How Has This Been Tested?
I have tested whether the session is updated in the browser and a new cookie is written.
Checklist: