[keycloak-user] Extending Themes via SPI

[Sarp Kaya]

Okay but what you are saying is done directly on the Keycloak source code which is then built and deployed, rather than extending classes and then deploying directly to a Keycloak instance?

From: Stian Thorgersen <sthorger at redhat.com<mailto:sthorger at redhat.com>>
Reply-To: "stian at redhat.com<mailto:stian at redhat.com>" <stian at redhat.com<mailto:stian at redhat.com>>
Date: Friday, February 12, 2016 at 6:29 PM
To: Abdullah Sarp Kaya <akaya at expedia.com<mailto:akaya at expedia.com>>
Cc: "keycloak-user at lists.jboss.org<mailto:keycloak-user at lists.jboss.org>" <keycloak-user at lists.jboss.org<mailto:keycloak-user at lists.jboss.org>>
Subject: Re: [keycloak-user] Extending Themes via SPI

There's a lot more to the login on Keycloak than a simple JSP page used for JEE form-based authentication. We have user registration, password recovery, OTP support, remember me, etc, etc..

Take the look and feel (stylesheet) of your JSP login screen and apply it to Keycloak with a custom theme. That's the simplest, quickest and best option.

On 12 February 2016 at 09:15, Sarp Kaya <akaya at expedia.com<mailto:akaya at expedia.com>> wrote:

We have internal front end libraries that works with JSP only. From the sounds of SPI, I thought that I could use JSP and our internal libraries instead of FreeMarker templates. Also because our JSP login screen is almost ready it wouldn't take much time to just deploy it (that's what I thought).

From: Stian Thorgersen <sthorger at redhat.com<mailto:sthorger at redhat.com>>
Reply-To: "stian at redhat.com<mailto:stian at redhat.com>" <stian at redhat.com<mailto:stian at redhat.com>>
Date: Friday, February 12, 2016 at 5:54 PM
To: Abdullah Sarp Kaya <akaya at expedia.com<mailto:akaya at expedia.com>>
Cc: "keycloak-user at lists.jboss.org<mailto:keycloak-user at lists.jboss.org>" <keycloak-user at lists.jboss.org<mailto:keycloak-user at lists.jboss.org>>
Subject: Re: [keycloak-user] Extending Themes via SPI

What are you actually trying to achieve? We mainly support modifying the FreeMarker templates and stylesheets. Beyond that you may in theory be able to re-implement it all to replace FreeMarker with something else, but I don't see why you would want to and it would be a significant amount of work, and also maintenance.

On 12 February 2016 at 07:08, Sarp Kaya <akaya at expedia.com<mailto:akaya at expedia.com>> wrote:
Hi all,

In regards to Extending Themes via SPI all I found is this documentation:
http://keycloak.github.io/docs/userguide/keycloak-server/html/providers.html and
<http://keycloak.github.io/docs/userguide/keycloak-server/html/themes.html#d4e2450>
http://keycloak.github.io/docs/userguide/keycloak-server/html/themes.html#d4e2450
I found it a little less describing.

When I implement those two classes, where do I put the new implemented classes? How do I deploy them?
Can I also use Spring mvc and JSP and few maven dependencies instead of freemarker?

I also tried to find an example to extend theme using SPI but there seems to be none. It would be really nice if you could provide a sample hello world.

Thank you very much,
Sarp Kaya

_______________________________________________
keycloak-user mailing list
keycloak-user at lists.jboss.org<mailto:keycloak-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user


_______________________________________________
keycloak-user mailing list
keycloak-user at lists.jboss.org<mailto:keycloak-user at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-user/attachments/20160212/9f809407/attachment-0001.html