On 12/9/2015 8:56 AM, Doug Szeto wrote:
We're looking to use Keycloak in an enterprise environment that
reinforces tight web restrictions. There are network guys combing over
every url, and dev ops guys doing other things with urls, and software
developers integrating Keycloak.
Customized theming is a big selling point because business people can
change up the look without worrying about most web attacks. But
operations people dislike tying urls to your release cycle, especially
when there are hot fixes.
Your Freemaker template is a little strange too because it
rewrites resource links as absolute urls, and make it behave strange
behind reverse proxies.
I understand your reasons for defaults, but allowing another flag for
prefixing custom theme web resources would integrate more easily with
other environments.
Other than possibly the absolute urls used by the Freemarker template,
all this doesn't sound like a technical issue you are having, but rather
possibly misguided opinions of your ops people. You are the only one
that has complained.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com