Keycloak 3.4.0.CR1 has SSL enabled out of the box as it builds on top of
WildFly 11.
As it's a self-signed certificate it's not secure and not that easy to use
though. Users would have to manually accept the cert in their browsers and
even worse they would have to import the cert into truststores for
applications. So it would make it harder to use in development even though
the cert is automatically generated.
On 2 October 2017 at 16:25, Bill Burke <bburke(a)redhat.com> wrote:
I'm not sure, but I believe the latest Wildfly can auto create an
SSL
certificate at boot time. Should we look into this prior to the end
of 3.4.1 and have realm SSL policies changed to reflect this? I never
liked the idea that SSL is turned off and realm SSL policies don't
require SSL by default.
--
Bill Burke
Red Hat
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev