KEYCLOAK-8310 Change scheme option to alwaysHttps option
This commit is contained in:
parent
47ef45dc1a
commit
10b2f2ef9a
1 changed files with 2 additions and 3 deletions
|
@ -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.
|
`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
|
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
|
correctly, or if there is an internal application using non-https to invoke {project_name}. In such cases it is possible
|
||||||
and you should strive to use `https` always. In this case you can set a fixed scheme as well by setting the `scheme`
|
to set the `alwaysHttps` to `true`.
|
||||||
property to `https`.
|
|
||||||
|
|
||||||
==== Custom provider
|
==== Custom provider
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue