Following up on this conversation. I was unable to find a way to do this
via the Freemarker templates unfortunately. The templates are not
receiving anything useful in determining the full path and query
parameters. The only approach that I've found to do what I need is to add
a small Javascript snippet to my theme that is able to look at the query
parameters and insert a new stylesheet reference into the code based on a
query parameter. Ugly, but seems effective assuming I can get my query
parameter set in all of the URL's that matter.
=================================
*Craig Setera*
*Chief Technology Officer*
On Wed, Aug 29, 2018 at 9:36 AM Craig Setera <craig(a)baseventure.com> wrote:
Dmitry,
I've put Keycloak on the back burner for the moment. I do intend to pick
it back up toward the end of the year and I expect I will be digging into
this heavily. If I figure anything out, I will be sure to report back.
Craig
=================================
*Craig Setera*
*Chief Technology Officer*
*415-324-5861**craig(a)baseventure.com <craig(a)baseventure.com>*
On Wed, Aug 1, 2018 at 7:50 PM Dmitry Telegin <dt(a)acutus.pro> wrote:
> Craig, Will,
>
> Sorry for having fooled you :-\ turns out that the ${url} object is
> actually not what it seems.
>
> I'd suggest the following trick. Could someone please try dumping all the
> available FTL variables using the below approach?
>
>
https://community.liferay.com/blogs/-/blogs/the-magic-template-variable-d...
>
> This is for Liferay, but I hope it works with Keycloak FTLs without any
> major modifications. So hopefully we can fish something useful out of there.
>
> Cheers,
> Dmitry Telegin
> CTO, Acutus s.r.o.
> Keycloak Consulting and Training
>
> Pod lipami street 339/52, 130 00 Prague 3, Czech Republic
> +42 (022) 888-30-71
> E-mail: info(a)acutus.pro
>
> On Tue, 2018-07-31 at 14:13 -0700, Will Lopez wrote:
> > Hi Dmitry,
> >
> > I have a use case for this same need: conditionally rendering a block
> of HTML in in the login.ftl based on the value of a query string param.
> >
> > I have an a question with more details here:
>
https://stackoverflow.com/questions/51619158/keycloak-make-query-string-p...
> >
> > I attempted to use ${ur} as you suggested, however it does not have a
> public method that provides the request url :(
> >
> >
>
https://github.com/keycloak/keycloak/blob/master/services/src/main/java/o...
> >
> > I am missing something? Or is there any other way to access the login
> request url in login.ftl?
> >
> > Thanks, Will
> >
> > > > > On Jul 30, 2018, at 9:25 PM, Dmitry Telegin
<dt(a)acutus.pro>
> wrote:
> > >
> > > Hi Craig, sorry for late response,
> > >
> > > On Thu, 2018-07-12 at 06:08 -0500, Craig Setera wrote:
> > > > We build and host a multitenant application that is currently using
> > > > homegrown authentication and authorization (using Picketlink). We
> are
> > > > considering a move to Keycloak. My preference would be to use the
> login
> > > > flows that are built in to Keycloak rather than building our own,
> however
> > > > that is dependent on whether we can properly brand those login
> flows on a
> > > > per-customer basis in some dynamic way.
> > >
> > > In Keycloak parlance, the term "login flow" has a very
particular
> > > meaning. Basically, it's what you see in the Authentication section in
> > > the Admin Console. It defines how authentication *works* rather than
> > > how it *looks like* (i.e. logic rather than appearance).
> > >
> > > Do you really mean "login flows"? From the second part of your
message
> > > I can deduce you're mainly interested in customizing the GUI.
> > >
> > > > In looking at the theme SPI support, it appears to be mostly
> targeted to
> > > > supporting mulitple "static" themes. Is it possible to make
a
> theme that
> > > > is dynamic based on, for example, a query parameter?
> > >
> > > By default, Keycloak uses FreeMarker templates for login screens. In
> > > the templates, the URL object is exposed as ${url}, so you can analyze
> > > it and add conditional statements. If you're ok with that, probably
> you
> > > won't need to implement any SPIs.
> > >
> > > Otherwise, you can either implement custom theme selection logic based
> > > on request parameters (Theme Selector SPI), or completely redefine
> > > theming mechanism (Theme SPI).
> > >
> > > > Are there any
> > > > examples anywhere on how that might be possible?
> > >
> > > Well, builtin Keycloak themes are the best example IMO :) you can find
> > > the default login theme under
> > > themes/src/main/resources/theme/base/login in the source tree.
> > >
> > > > Would Keycloak carry
> > > > through query parameters if they were provided when launching the
> login
> > > > flow?
> > >
> > > It's best to create a custom theme and see :)
> > >
> > > Good luck!
> > > Dmitry Telegin
> > > CTO, Acutus s.r.o.
> > > Keycloak Consulting and Training
> > >
> > > Pod lipami street 339/52, 130 00 Prague 3, Czech Republic
> > > +42 (022) 888-30-71
> > > E-mail: info(a)acutus.pro
> > >
> > > > Thanks,
> > > > Craig
> > > > _______________________________________________
> > > > keycloak-user mailing list
> > > > keycloak-user(a)lists.jboss.org
> > > >
https://lists.jboss.org/mailman/listinfo/keycloak-user
> > > _______________________________________________
> > > keycloak-user mailing list
> > > keycloak-user(a)lists.jboss.org
> > >
https://lists.jboss.org/mailman/listinfo/keycloak-user
> >
> >
>