⬆️v8 -> v9
If it's not already the case you must now use the
copy-keycloak-resources-to-public
postinstall script. (Only in WebPack projects, with Vite it's done automatically by the plugin)!.The
keycloakVersionDefaultAssets
has been removed in favor ofloginThemeResourcesFromKeycloakVersion
.You now must have
mvn
(Maven,brew install maven
) installed to build your Keycloakify theme. Thebundler
build option has been removed in favor of doCreateJar. (Note that Maven is present by default on the GitHub Action runners). If you are building your theme within Docker here are the instructions.The
extraThemeNames
build option has been removed, if you have theme variant, simply pass an array to the themeName option.Keycloakify now generates two jars
*.jar
andretrocompat-*.jar
. You should update your CI.If you have no Account theme: You can use the
retrocompat-*.jar
, it will work on any Keycloak version.If you have an Account theme:
You should use
retrocompat-*.jar
on any Keycloak version prior to 23. And select<your theme>_retrocompat
when selecting in the dropdown when selecting your account theme.You should use
*.jar
on Keycloak 23 and up.
Be aware that Acount theme does not work in Keycloak 22 (and only in this version).
If you where loading your theme into your Keycloak by copy pasting the build_keycloak/src directly into your Keycloak you can still do that with Keycloak prior to 22 or if you don't have an account theme but if you have an account theme and you are on Keycloak 23 you must follow one of the official instruction for loading the .jar into Keycloak.
Last updated