Replace removed p1-sso theme in the imported test realm
Bug
Description
The imported test realm in docs/test-data/realm.json still selects p1-sso for loginTheme, accountTheme, and adminTheme. The P1 auth plugin removed this legacy theme in 3.7.32; the plugin bundles p1-sso-v2 instead.
Importing the realm with plugin 3.7.32 produces:
Failed to find LOGIN theme p1-sso, using built-in themesThe login page falls back to keycloak.v2, so package SSO tests no longer exercise the intended P1 theme.
Reproduce by deploying the package SSO test environment with plugin 3.7.32, importing the existing realm, and opening an application login flow. Check the Keycloak logs and served login theme assets.
References:
BigBang Version
Reproduced during local monitoring package testing against a Big Bang 3.34.0 development branch, with Keycloak 26.8.0 and P1 auth plugin 3.7.32.
Impact
Package tests importing this realm silently use a fallback login theme. Older Cypress selectors restricted to input elements also fail with the current login/accept buttons. Selecting p1-sso-v2 fixes the missing-theme configuration, but those selectors still require updating.
Suggested fix
Change the realm's loginTheme, accountTheme, and adminTheme to p1-sso-v2; retain emailTheme: keycloak. A candidate fix is already pushed.
Local testing with the updated realm confirmed p1-sso-v2 login assets, no missing-login-theme error, and all 12 monitoring Cypress checks passing with the updated selectors. Umbrella consumers pinned to the old realm revision need a follow-up pin update.
Acceptance Criteria
- Replace all three removed
p1-ssotheme selections withp1-sso-v2in the test realm. - Import the updated realm with the supported plugin and verify login uses
p1-sso-v2without a missing-theme fallback. - Validate the configured account/admin themes resolve successfully.
- Run package SSO tests with selectors compatible with the rendered buttons.
- Track the umbrella realm import pin update.