Thank you, will give it another try.
On Wed, Jan 20, 2016 at 4:59 PM, Stian Thorgersen <sthorger(a)redhat.com> wrote:
keycloak.json already supports system properties, I think it
supports
environment variables as well "${env.KEYCLOAK}"
On 20 January 2016 at 19:57, Juraci Paixão Kröhling <juraci(a)kroehling.de>
wrote:
>
> On 20.01.2016 19:15, Bruno Oliveira wrote:
> > I noticed that looking at Hawkular, but correct if I'm wrong. Today
> > that's not supported for the client side configuration, unless you
> > workaround it like you did with Servlets, right?
>
> Right, for the JavaScript Adapter (which loads /keycloak.json by
> default), you'd need a workaround like that.
>
> For the Wildfly adapter, it's already supported on the secure-deployment
> approach. So, instead of using a keycloak.json within your WAR, you can
> protect it via the subsystem.
>
> Not sure about other adapters, though.
>
> - Juca.
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev