Skip to content

fix(keycloak): account console 500 — stop forcing 'airavata' as global default theme#693

Merged
yasithdev merged 1 commit into
apache:masterfrom
yasithdev:fix-keycloak-account-console
Jun 15, 2026
Merged

fix(keycloak): account console 500 — stop forcing 'airavata' as global default theme#693
yasithdev merged 1 commit into
apache:masterfrom
yasithdev:fix-keycloak-account-console

Conversation

@yasithdev

Copy link
Copy Markdown
Contributor

Summary

The devstack Keycloak ran with --spi-theme-default=airavata. The airavata theme only ships a login variant, so making it the global default also made it the default account theme. Keycloak's account console then 500s with a NullPointerException (Failed to find ACCOUNT theme airavataAccountLoader.getAccountResourceProvider NPE), which broke the Django portal's User Settings link (it lands on a Keycloak "internal server error" page).

Fix

Remove the --spi-theme-default=airavata flag. The default realm already pins loginTheme: airavata, so login branding is unchanged; account/admin/email fall back to Keycloak's built-in themes and the account console works.

Test plan

  • https://auth.airavata.host/realms/default/account/ returns HTTP 200 (was 500) after tilt recreated the keycloak container; no account-theme NPE in logs.
  • Browser: the URL now loads the airavata-branded Keycloak sign-in for the account-console client and lands on the user profile after auth.
  • Login page still renders the airavata theme.

The devstack set --spi-theme-default=airavata, but the airavata theme only ships
a login variant. That also made airavata the default ACCOUNT theme, so Keycloak's
account console returned HTTP 500 with a NullPointerException (account theme
'airavata' not found) — breaking the portal's User Settings link. The default
realm already pins loginTheme: airavata, so removing the global default keeps
login branding intact while account/admin/email fall back to Keycloak's built-in
themes.
@yasithdev yasithdev merged commit 5a62c0f into apache:master Jun 15, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant