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

fix relevant options for existing guides (#9805)

Browse source 
closes #9804
This commit is contained in:
Dominik Guhr 2022-01-27 10:03:11 +01:00 committed by GitHub
parent ef134390c2
commit 0f082dde5b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/src/main/server/db.adoc
View file

@ -7,7 +7,7 @@
title="Relational database setup" title="Relational database setup"
summary="Understand how to configure different relational databases for Keycloak" summary="Understand how to configure different relational databases for Keycloak"
priority=10 priority=10
includedOptions="db db.* hostname"> includedOptions="db db-* hostname">
First step is to decide which database vendor you are going to use. Keycloak has support for a number of different vendors. First step is to decide which database vendor you are going to use. Keycloak has support for a number of different vendors.

2
docs/guides/src/main/server/enabletls.adoc
View file

@ -4,7 +4,7 @@
<@tmpl.guide <@tmpl.guide
title="Configure TLS" title="Configure TLS"
summary="Learn how to configure Keycloak's https certificates for in- and outgoing requests as well as mTLS." summary="Learn how to configure Keycloak's https certificates for in- and outgoing requests as well as mTLS."
includedOptions="https.* http.enabled"> includedOptions="https-* http-enabled">
Transport Layer Security (short: TLS) is crucial to exchange data over a secured channel. For production environments, you should never expose Keycloak endpoints through HTTP, as sensitive data is at the core of what Keycloak exchanges with other applications. In this guide you will learn how to configure Keycloak to use HTTPS/TLS. Transport Layer Security (short: TLS) is crucial to exchange data over a secured channel. For production environments, you should never expose Keycloak endpoints through HTTP, as sensitive data is at the core of what Keycloak exchanges with other applications. In this guide you will learn how to configure Keycloak to use HTTPS/TLS.

2
docs/guides/src/main/server/proxy.adoc
View file

@ -6,7 +6,7 @@
title="Configuring a reverse proxy" title="Configuring a reverse proxy"
summary="Learn how to configure Keycloak together with a reverse proxy, api gateway or load balancer." summary="Learn how to configure Keycloak together with a reverse proxy, api gateway or load balancer."
priority=20 priority=20
includedOptions="proxy proxy.*"> includedOptions="proxy proxy-*">
It is pretty common nowadays to use a reverse proxy in distributed environments. If you want to use Keycloak together with such a proxy, you can use different proxy modes depending on the TLS termination in your specific environment: It is pretty common nowadays to use a reverse proxy in distributed environments. If you want to use Keycloak together with such a proxy, you can use different proxy modes depending on the TLS termination in your specific environment: