<p dir="ltr">Do you not have to extend it to enable SSL in any case? So you export the extra port then right</p>
<div class="gmail_quote">On 17 Feb 2016 13:24, "Kevin Thorpe" <<a href="mailto:kevin@pibenchmark.com">kevin@pibenchmark.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Its easy to make your own image on top to expose that port. However in our case we use keycloak inside docker on 8080 and front it externally with our main nginx SSL+load balancer</p>
<div class="gmail_quote">On 17 Feb 2016 12:31 pm, "Tim Dudgeon" <<a href="mailto:tdudgeon.ml@gmail.com" target="_blank">tdudgeon.ml@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can the SSL port on the docker images be exposed?<br>
Currently only port 8080 is exposed. Why not 8443?<br>
<br>
Tim<br>
_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org" target="_blank">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>_______________________________________________<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>