Fix SSO integration for Rancher (!7890) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

The aim of this MR is to fix the issue describe in #4003 (closed), taking the sso implementation step-by-step I've noticed that we have inconsistences into rancher client definition comparing with the official documentation.

Mapper details for group_path in our setup:

And into documentation:

More details here: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-keycloak-oidc.

Test coverage

Changed the rancher client configuration in order to be aligned with the upstream documentation and I've tested it running sso test script in loop:

 for i in {1..15}; do pytest ./tools/login-test/test_sso_playwright.py --browser firefox -v --tb=short; done
========================================================================================================== test session starts ==========================================================================================================
platform linux -- Python 3.12.9, pytest-8.4.1, pluggy-1.6.0 -- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /root/sylva-rancher
plugins: playwright-0.7.0, base-url-2.1.0
collected 8 items

tools/login-test/test_sso_playwright.py::test_rancher_sso[firefox] PASSED

pytest ./tools/login-test/test_download_workload_kubeconfig.py --browser firefox -v --tb=short
========================================================================================================== test session starts ==========================================================================================================
platform linux -- Python 3.12.9, pytest-8.4.1, pluggy-1.6.0 -- /usr/bin/python3
cachedir: .pytest_cache
rootdir: /root/sylva-rancher
plugins: playwright-0.7.0, base-url-2.1.0
collected 1 item

tools/login-test/test_download_workload_kubeconfig.py::test_rancher_download_workload_kubeconfig[firefox] PASSED                                                                                                                  [100%]

========================================================================================================== 1 passed in 11.11s ===========================================================================================================

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited May 22, 2026 by Thomas Morin

Fix SSO integration for Rancher

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports