Done
Details
Assignee
Pavel FilippovPavel FilippovReporter
Yauhen VavilkinYauhen VavilkinPriority
P2Story Points
0.5Sprint
NoneDevelopment Team
EurekaFix versions
Release
Ramsons (R2 2024) Service Patch #1TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Pavel Filippov
Pavel FilippovReporter
Yauhen Vavilkin
Yauhen VavilkinPriority
Story Points
0.5
Sprint
None
Development Team
Eureka
Fix versions
Release
Ramsons (R2 2024) Service Patch #1
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 30, 2025 at 12:48 PM
Updated February 20, 2025 at 2:14 PM
Resolved January 30, 2025 at 2:34 PM
Overview
Upgrade to Keycloak v26.0.X.
See:
and
(There was no 26.0.3)
From the Release notes:
Also:
Scope
Upgrade folio-keycloak base image
Work with devops / QA to ensure we haven’t introduced any regressions/problems.
Including with custom themes, and plugins/extensions (e.g. for automatic IdP link creation)
Upgrade keycloak client version where applicable? (e.g. mgr-*, sidecar, mod-*-keycloak, etc.)
Q: should we put this in scope of this task? Create one Jira to update the clients? Create distinct JIRAs for each affected component?
Acceptance Criteria
A new folio-keycloak image based on keycloak 26.x has been built and is available
QA has run at least smoke tests against an environment running the new image (e.g. etesting-snapshot).