Yep, the old approach was more convenient. With local VMs you'll most likely be using a IP address in the range that we permit non-https to when set to external (http://en.wikipedia.org/wiki/Private_network). For PaaS (i.e. OpenShift) the provider usually sets up https for you so it's not a problem, but I guess the remaining issue is for IaaS (i.e. AWS). If there's demand for it we could add some mechanism to disable it for dev without having to use the admin console.

----- Original Message -----
> From: "Christina Lau" <christinalau28@icloud.com>
> To: keycloak-user@lists.jboss.org
> Sent: Tuesday, 26 August, 2014 10:20:21 PM
> Subject: Re: [keycloak-user] Unable to start Keycloak beta on AWS VM -        HTTPS   required
>

> Thx. I was able to zip up my laptop version and ssh over to make it work
> (i.e. bring up admin console). With RHEL VMs, there is no easy way to bring
> up a local browser so the old defaults were more convenient for those that
> do dev/test in the cloud.
> _______________________________________________
> keycloak-user mailing list
> keycloak-user@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>
_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user