libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

Fix wrong reverse proxy link (#11687)

Browse source 
Closes: #11626
This commit is contained in:
Salih Candir 2022-04-27 11:41:19 +02:00 committed by GitHub
parent e3f3e65ac5
commit 37134ec8b0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/guides/src/main/server/hostname.adoc
View file

@ -53,7 +53,7 @@ Otherwise, leave this parameter as false to allow internal applications to commu
To reduce attack surface, the administration endpoints for Keycloak and the Admin Console should not be publicly accessible.
Therefore, you can secure them by using a reverse proxy.
For more information about which paths to expose using a reverse proxy, see the <@links.server id="proxy"/> Guide.
For more information about which paths to expose using a reverse proxy, see the <@links.server id="reverseproxy"/> Guide.
== Overriding the hostname path
When running Keycloak behind a reverse proxy, you may expose Keycloak using a different context path such as `myproxy.url/mykeycloak`.
@ -62,7 +62,7 @@ To perform this action, you can override the hostname path to use the path defin
<@kc.start parameters="--hostname=myurl --hostname-path=mykeycloak"/>
The `hostname-path` configuration takes effect when a reverse proxy is enabled.
For details, see the <@links.server id="proxy"/> Guide.
For details, see the <@links.server id="reverseproxy"/> Guide.
== Using the hostname in development mode
You run Keycloak in development mode by using `start-dev`.