We are planning to make the admin console/endpoints exposed on a separate bind address and port in the future, but for now this has to be done with a proxy/loadbalancer/firewall.

On 3 May 2016 at 07:41, Thomas Connolly <thomas_connolly@yahoo.com> wrote:

Hi

Please advise on the approach to deploying KC where the Admin GUI and APIs are not exposed.

We want to control what is exposed onto the internet and what is available within the organisation.
The flows are exposed but the admin gui / api are only accessible within the organisation.

Currently we're considering filtering at the load balancer essentially whitelisting traffic.
The admin GUI is accessed internally within the organisation.

Alternatively is there a way to config off admin ui & api and only deploy this into production? With the admin deployed internally?

Regards Tom Connolly.

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user