From 10b2f2ef9a50a92023c6b6f3f261768a54b4aeac Mon Sep 17 00:00:00 2001 From: stianst Date: Tue, 9 Oct 2018 19:48:06 +0200 Subject: [PATCH] KEYCLOAK-8310 Change scheme option to alwaysHttps option --- server_admin/topics/threat/host.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/server_admin/topics/threat/host.adoc b/server_admin/topics/threat/host.adoc index 18b763e044..0ed0ee6c72 100644 --- a/server_admin/topics/threat/host.adoc +++ b/server_admin/topics/threat/host.adoc @@ -88,9 +88,8 @@ it should not be necessary to change this. It is possible to configure fixed por `httpsPort` properties on the fixed provider. In most cases the scheme should be set correctly. This may not be true if the reverse proxy is unable to set the `X-Forwarded-For` header -correctly, or if there is an internal application using non-https to invoke {project_name}. The latter is not recommended -and you should strive to use `https` always. In this case you can set a fixed scheme as well by setting the `scheme` -property to `https`. +correctly, or if there is an internal application using non-https to invoke {project_name}. In such cases it is possible +to set the `alwaysHttps` to `true`. ==== Custom provider