This package provides a login theme named sdohplace-discovery for Keycloak. It keeps the default Keycloak login layout and only adjusts branding:
Nunito/Fredokafont pairing- SDOH Place color palette
- decorative background accents
- project logo above the login header
Copy the theme/sdohplace-discovery directory into the Keycloak server themes/ directory.
If you prefer an archive deployment, package this folder structure into a JAR with:
META-INF/keycloak-themes.jsontheme/sdohplace-discovery/login/...
Then place that JAR in the Keycloak providers/ directory.
- Open the Keycloak Admin Console.
- Select your realm.
- Open
Realm settings. - Open the
Themestab. - Set
Login themetosdohplace-discovery. - Save.
Run a local Keycloak preview server from this folder:
docker compose upThen open:
http://localhost:8080- Admin login:
admin/admin
After Keycloak starts:
- Open the Admin Console.
- Create or select a test realm.
- Open
Realm settings→Themes. - Set
Login themetosdohplace-discovery. - Save.
- Open the realm login page and refresh while editing
theme/sdohplace-discovery/login/resources/css/styles.css.
If theme changes do not appear immediately, restart Keycloak with theme caching disabled for development, or clear the server cache directory data/tmp/kc-gzip-cache before restarting.
These steps require cluster admin access on the software-dev cluster
Switch your Kubernetes context to the software-dev cluster:
% kubectl config use-context software-dev
Switched to context "software-dev".Ensure that your token is valid before continuing:
% kubectl get pods -n keycloak
NAME READY STATUS RESTARTS AGE
kc-themes-explorer 1/1 Running 0 5s
keycloak-0 1/1 Running 323 164d
keycloak-postgresql-0 1/1 Running 4 (106d ago) 164d
move-keycloak-theme-69xdz 0/1 Error 0 164d
move-keycloak-theme-9m92t 0/1 Error 0 164d
move-keycloak-theme-gl8p2 0/1 Error 0 164d
move-keycloak-theme-gsjtk 0/1 Error 0 164d
move-keycloak-theme-t2dnx 0/1 Error 0 164d
rsync-data-keycloak-postgresql-0-g8zlv 0/1 Completed 0 164dNOTE: if you see a 403 error when running kubectl get pods, then your token has likely expired.
When this happens: Login to Rancher, choose the software-dev cluster, and click "Download KubeConfig" at the top-right corner. Replace your existing token in ~/.kube/config with the value from the newly-downloaded file.
Create a kc-themes-explorer Pod if it does not already exist (no-op if it exists):
% kubectl apply -f pvc-explorer.keycloak.software-dev.yaml -n keycloak
pod/kc-themes-explorer createdOnce it starts, shell into the container:
% kubectl exec -it kc-themes-explorer -n keycloak -- bash
root@kc-themes-explorer:/opt#Within the container, run the following commands:
apt-get update && apt-get install ca-certificates git
git clone https://github.com/healthyregions/sdohplace-keycloak-theme
mv sdohplace-keycloak-theme/theme/sdohplace-discovery/ ../bitnami/keycloak/themes/This will install git, then clone/copy our new theme folder into the list of "themes" that Keycloak can see 🎉