fix(keycloak): account console 500 — stop forcing 'airavata' as global default theme#693
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The devstack Keycloak ran with
--spi-theme-default=airavata. Theairavatatheme 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 aNullPointerException(Failed to find ACCOUNT theme airavata→AccountLoader.getAccountResourceProviderNPE), which broke the Django portal's User Settings link (it lands on a Keycloak "internal server error" page).Fix
Remove the
--spi-theme-default=airavataflag. Thedefaultrealm already pinsloginTheme: 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) aftertiltrecreated the keycloak container; no account-theme NPE in logs.account-consoleclient and lands on the user profile after auth.