The benefits are that you can simply hot deploy by either using "mvn
wildfly:deploy" or copy the jar to standalone/deployments. No need to
create the module structure, restart the server, edit standalone.xml to
register the module, etc.. You can also package a custom theme alongside
any custom providers if you have any.
On 5 April 2018 at 11:31, Federico Navarro Polo - Info.nl <federico(a)info.nl>
Are there any examples in the documentation about adding theme resources
or using theme selector SPI?
In our case, we used to install theme as a module, which was the
recommended way, so it’s not entirely clear what advantages brings the new
On 23/03/18 12:00, "keycloak-user-bounces(a)lists.jboss.org on behalf of
Stian Thorgersen" <keycloak-user-bounces(a)lists.jboss.org on behalf of
I missed one cool new feature. We also now have support for UMA 2.0
including allowing users to manage resource permissions in the account
On Thu, 22 Mar 2018, 21:04 Stian Thorgersen, <sthorger(a)redhat.com>
> I'm very pleased to announce the first release of Keycloak 4!
> To download the release go to the Keycloak homepage
> HighlightsBrand new login pages
> The login pages have received a brand new look. They now look much
> modern and clean!
> Themes and Theme Resources
> It's now possible to hot-deploy themes to Keycloak through a regular
> provider deployment. We've also added support for theme resources.
> resources allows adding additional templates and resources without
> a theme. Perfect for custom authenticators that require additional
> added to the authentication flow.
> We've also added support to override the theme for specific clients.
> that doesn't cover your needs, then there's a new Theme Selector SPI
> allows you to implement custom logic to select the theme.
> Native promise support to keycloak.js
> has support for the old style promises as well. Both can be used
> Edit links in documentation
> To make it easier to contribute changes to the documentation we have
> links to all sections of the documentation. This brings you straight
> GitHub editor for the relevant AsciiDoctor file. There's also a
> to report an issue on a specific page that will include the relevant
> in the description.
> HTTPS support on keycloak.org
> Thanks to GitHub pages and Let's Encrypt there's finally HTTPS on
. About time?
> Loads more..
> The full list of resolved issues is available in JIRA
> Before you upgrade remember to backup your database and check the
> guide <http://www.keycloak.org/docs/latest/upgrading/index.html>
> anything that may have changed.
keycloak-user mailing list