fix: removes deprecated config option for strict https and updates Keycloak bootstrap#1
Open
fix: removes deprecated config option for strict https and updates Keycloak bootstrap#1
Conversation
…otstrap to use supported option
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
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.
Keycloak 26 deprecated the KC_HOSTNAME_STRICT_HTTPS environment variable, silently ignoring it. As a result, both the master and opencase realms initialized with the default sslRequired=EXTERNAL mode. This made local deployments basically non-functional.
The fix replaces the unsupported environment variable with a new KEYCLOAK_SSL_REQUIRED setting that is applied directly to both Keycloak realms during OpenCASE's bootstrap sequence. It defaults to
nonein development andexternalin production, preserving HTTPS enforcement for partner deployments while allowing plain HTTP locally.