This is an automated email from the ASF dual-hosted git repository.

yasithdev pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/airavata.git


The following commit(s) were added to refs/heads/master by this push:
     new 5a62c0f429 fix(keycloak): stop forcing 'airavata' as the global 
default theme (#693)
5a62c0f429 is described below

commit 5a62c0f4295704bc4fc811af65bc4e954d7738f7
Author: Yasith Jayawardana <[email protected]>
AuthorDate: Sun Jun 14 20:07:19 2026 -0400

    fix(keycloak): stop forcing 'airavata' as the global default theme (#693)
    
    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.
---
 compose.yml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/compose.yml b/compose.yml
index 222ac6008a..e48c0d902f 100644
--- a/compose.yml
+++ b/compose.yml
@@ -60,7 +60,11 @@ services:
       - --health-enabled=true
       - --metrics-enabled=true
       - --log-level=INFO
-      - --spi-theme-default=airavata
+      # Don't force "airavata" as the global default theme: it only ships a
+      # `login` variant, so making it the default ACCOUNT/admin/email theme 
makes
+      # Keycloak's account console 500 (NPE: account theme "airavata" not 
found).
+      # The realm pins `loginTheme: airavata` explicitly, so login branding is
+      # unaffected; account/admin/email use Keycloak's built-in themes.
     networks:
       - airavata-devstack
     healthcheck:

Reply via email to