[release/13.3] Fix Keycloak HTTPS primary endpoint#17063
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 17063Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 17063" |
Contributor
|
Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
|
Contributor
|
🎬 CLI E2E Test Recordings — 67 recordings uploaded (commit View all recordings
📹 Recordings uploaded automatically from CI run #25832616423 |
davidfowl
approved these changes
May 14, 2026
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.
Backport of #17058 to release/13.3
/cc @danegsta
Customer Impact
Makes a (breaking) change to Keycloak to upgrade the primary endpoint to HTTPS instead of adding a second endpoint when developer certificates are enabled. Also changes the primary endpoint name to "http" to allow standard service discovery
http+https://<keycloakservice>style URLs. This fixes an issue where Keycloak tokens became invalid after an app host restart due to the HTTPS endpoint port being dynamic.Testing
Manual and automated tests
Risk
It's a breaking change, but for a good reason. I've done proper smoke tests to validate that this fixes the underlying issue.
Regression?
No