Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Keycloak version to 26.x #5381

Open
mesembria opened this issue Jan 29, 2025 · 0 comments
Open

Upgrade Keycloak version to 26.x #5381

mesembria opened this issue Jan 29, 2025 · 0 comments
Labels
P1 Fix Soon: High priority items that should be considered in the next Sprint planning cycle

Comments

@mesembria
Copy link
Contributor

Keycloak has released a major upgrade, version 26.0.0. We should upgrade our infrastructure to use the latest version.

https://www.keycloak.org/docs/latest/upgrading/index.html#migrating-to-26-0-0

Noting some changes we need to make when upgrading:

In the Keycloak theme, change the paths of external resources
-styles=web_modules/@fontawesome/fontawesome-free/css/icons/all.css web_modules/@patternfly/react-core/dist/styles/base.css web_modules/@patternfly/react-core/dist/styles/app.css node_modules/patternfly/dist/css/patternfly.min.css node_modules/patternfly/dist/css/patternfly-additions.min.css css/login.css css/styles.css
+styles=web_modules/@fontawesome/fontawesome-free/css/icons/all.css web_modules/@patternfly/react-core/dist/styles/base.css web_modules/@patternfly/react-core/dist/styles/app.css vendor/patternfly-v3/css/patternfly.min.css vendor/patternfly-v3/css/patternfly-additions.min.css css/login.css css/styles.css
In the helm chart, remove proxy: edge and replace it with proxyHeaders https://www.keycloak.org/docs/latest/upgrading/index.html#deprecated-proxy-option
(TBD) We may need to change how we set up an admin user, see https://www.keycloak.org/server/bootstrap-admin-recovery and https://www.keycloak.org/docs/latest/upgrading/index.html#admin-bootstrapping-and-recovery

@mesembria mesembria moved this to Backlog in Planned Work Jan 29, 2025
@mesembria mesembria added the P1 Fix Soon: High priority items that should be considered in the next Sprint planning cycle label Jan 29, 2025
@mesembria mesembria moved this from Backlog to Ready in Planned Work Jan 30, 2025
@eleftherias eleftherias moved this from Ready to Backlog in Planned Work Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Fix Soon: High priority items that should be considered in the next Sprint planning cycle
Projects
Status: Backlog
Development

No branches or pull requests

1 participant