6:30 a.m.
Can the SSL port on the docker images be exposed?
Currently only port 8080 is exposed. Why not 8443?
Tim
7:23 a.m.
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
On 17 Feb 2016 12:31 pm, "Tim Dudgeon" <tdudgeon.ml(a)gmail.com> wrote:
Can the SSL port on the docker images be exposed?
Currently only port 8080 is exposed. Why not 8443?
Tim
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
8:16 a.m.
Do you not have to extend it to enable SSL in any case? So you export the
extra port then right
On 17 Feb 2016 13:24, "Kevin Thorpe" <kevin(a)pibenchmark.com> wrote:
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
On 17 Feb 2016 12:31 pm, "Tim Dudgeon" <tdudgeon.ml(a)gmail.com> wrote:
> Can the SSL port on the docker images be exposed?
> Currently only port 8080 is exposed. Why not 8443?
>
> Tim
> _______________________________________________
> 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
11:17 a.m.
Not sure if it helps, but I did this long time ago with WildFly:
https://github.com/jboss-dockerfiles/aerogear/blob/master/wildfly/Dockerfile.
Is not that hard to extend the image, also take a look at the script to
generate a self-signed certificate
https://github.com/jboss-dockerfiles/aerogear/blob/master/wildfly/configu...
.
On Fri, Feb 19, 2016 at 12:16 PM Stian Thorgersen <sthorger(a)redhat.com>
wrote:
Do you not have to extend it to enable SSL in any case? So you export
the
extra port then right
On 17 Feb 2016 13:24, "Kevin Thorpe" <kevin(a)pibenchmark.com> wrote:
> 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
> On 17 Feb 2016 12:31 pm, "Tim Dudgeon" <tdudgeon.ml(a)gmail.com>
wrote:
>
>> Can the SSL port on the docker images be exposed?
>> Currently only port 8080 is exposed. Why not 8443?
>>
>> Tim
>> _______________________________________________
>> 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
>
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
3025
days inactive
3027
days old
3 comments
4 participants
participants (4)
-
Bruno Oliveira -
Kevin Thorpe -
Stian Thorgersen -
Tim Dudgeon