Fix Keycloak configuration for WSL compatibility#2
Merged
jayblanc merged 2 commits intojayblanc:mainfrom Dec 5, 2025
Merged
Conversation
Contributor
|
Also usefull for none WSL user 😄 |
jayblanc
approved these changes
Dec 5, 2025
LucieLaury
pushed a commit
to LucieLaury/mbyte
that referenced
this pull request
Mar 19, 2026
Fix Keycloak configuration for WSL compatibility
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
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.
Ajout de la variable d'environnement KC_HTTP_ENABLED: true au service Keycloak pour permettre le fonctionnement correct avec WSL (Windows Subsystem for Linux).
Changements
Service: keycloak
Variable ajoutée: KC_HTTP_ENABLED: true
Raison: Permet à Keycloak de fonctionner correctement dans un environnement WSL en activant explicitement le support HTTP
Contexte
Cette configuration est nécessaire pour que Keycloak accepte les connexions HTTP non sécurisées dans un environnement de développement WSL, en complément des autres variables de proxy déjà configurées (KC_PROXY: edge).
@jayblanc