chore: update keycloak #2706
Merged
chore: update keycloak #2706
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
|
@kvanzuijlen upstream problem resolved :) |
tuunit
approved these changes
Jul 18, 2024
jjlakis
pushed a commit
to jjlakis/oauth2-proxy
that referenced
this pull request
Oct 19, 2024
--------- Co-authored-by: tuunit <[email protected]>
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
Updates the Keycloak version in the docker-compose configuration
Motivation and Context
Updates Keycloak to the latest version, giving a more relevant example for current users
How Has This Been Tested?
Locally ran, only receiving a 502 Bad Gateway after authentication as oauth2-proxy apparently converts the alias to the local docker IP, see log message:
Error proxying to upstream server: dial tcp 172.25.0.2:8080: connect: connection refused@tuunit any ideas?
Checklist: