libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Update docs to enable downstream processing (#16595)

Browse source 
Relates to: #16475
This commit is contained in:
Alexander Schwartz 2023-02-08 15:33:43 +01:00 committed by GitHub
parent 5f39aeb590
commit 9ecd589690
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/src/main/server/configuration-production.adoc
View file

@ -22,7 +22,7 @@ In a production environment, Keycloak instances usually run in a private network
For details on the endpoint categories and instructions on how to configure the public hostname for them, see the <@links.server id="hostname"/> guide. For details on the endpoint categories and instructions on how to configure the public hostname for them, see the <@links.server id="hostname"/> guide.
== Reverse proxy in a distributed environment == Reverse proxy in a distributed environment
Apart from <<Setting the hostname for Keycloak>>, production environments usually include a reverse proxy / load balancer component. It separates and unifies access to the network used by your company or organization. For a Keycloak production environment, this component is recommended. Apart from <@links.server id="hostname"/>, production environments usually include a reverse proxy / load balancer component. It separates and unifies access to the network used by your company or organization. For a Keycloak production environment, this component is recommended.
For details on configuring proxy communication modes in Keycloak, see the <@links.server id="reverseproxy"/> guide. That guide also recommends which paths should be hidden from public access and which paths should be exposed so that Keycloak can secure your applications. For details on configuring proxy communication modes in Keycloak, see the <@links.server id="reverseproxy"/> guide. That guide also recommends which paths should be hidden from public access and which paths should be exposed so that Keycloak can secure your applications.

4
docs/guides/src/main/templates/links.adoc
View file

@ -1,3 +1 @@
<#macro server id> <#macro server id>link:{links_server_${id}_url}[{links_server_${id}_name}]</#macro>
link:{links_server_${id}_url}[{links_server_${id}_name}]
</#macro>