<div dir="ltr">DId you follow documentation at <a href="http://keycloak.github.io/docs/userguide/keycloak-server/html/server-installation.html#d4e394">http://keycloak.github.io/docs/userguide/keycloak-server/html/server-installation.html#d4e394</a></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 February 2016 at 12:53, Matthias Müller <span dir="ltr"><<a href="mailto:Matthias_Mueller@tu-dresden.de" target="_blank">Matthias_Mueller@tu-dresden.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Does anyone have experiences with Keycloak 1.9 in an Apache2 reverse<br>
proxy configuration?<br>
<br>
In my test setup I am running Keycloak as a standalone service on port<br>
8080. It is proxied behind an Apache HTTP Server that manages the SSL<br>
communication and forwards requests to localhost:8080. The Apache side<br>
of the proxy is working. However, the administration console web page<br>
(auth/admin/master/console/) still contains plain http://... links<br>
(should be: https://) to the JS components which, of course, is invalid.<br>
Obviously the Keycloak service does not see (or ignores) the X-Forwarded<br>
headers.<br>
<br>
Am I missing something here?<br>
<br>
Cheers,<br>
Matthias<br>
<br>
[1]:<br>
<a href="http://auth.domain.org/auth/resources/1.9.0.final/admin/keycloak/lib/select2-3.4.1/select2.js" rel="noreferrer" target="_blank">http://auth.domain.org/auth/resources/1.9.0.final/admin/keycloak/lib/select2-3.4.1/select2.js</a><br>
_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
</blockquote></div><br></div>