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

Fix minor typos in documentations (#13154)

Browse source 
Co-authored-by: Stian Thorgersen <stianst@gmail.com>
This commit is contained in:
Marc Wrobel 2022-08-26 08:07:59 +02:00 committed by GitHub
parent 518d318f0c
commit 827e6c0b20
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/src/main/operator/installation.adoc
View file

@ -43,7 +43,7 @@ kubectl apply -f https://raw.githubusercontent.com/keycloak/keycloak-k8s-resourc
kubectl apply -f https://raw.githubusercontent.com/keycloak/keycloak-k8s-resources/{version}/kubernetes/keycloakrealmimports.k8s.keycloak.org-v1.yml kubectl apply -f https://raw.githubusercontent.com/keycloak/keycloak-k8s-resources/{version}/kubernetes/keycloakrealmimports.k8s.keycloak.org-v1.yml
---- ----
After successfull CRD installation, install the Keycloak Operator deployment by running the following command: After successful CRD installation, install the Keycloak Operator deployment by running the following command:
[source,bash,subs="attributes+"] [source,bash,subs="attributes+"]
---- ----

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

@ -33,7 +33,7 @@ To select the proxy mode, enter this command:
== Configure the reverse proxy == Configure the reverse proxy
Some Keycloak features rely on the assumption that the remote address of the HTTP request connecting to Keycloak is the real IP address of the clients machine. Some Keycloak features rely on the assumption that the remote address of the HTTP request connecting to Keycloak is the real IP address of the clients machine.
When you have a reverse proxy or loadbalancer in front of Keycloak, this might not be the case, so please make sure your reverse proxy is configured correctly by performing these actions: When you have a reverse proxy or a load balancer in front of Keycloak, this might not be the case, so please make sure your reverse proxy is configured correctly by performing these actions:
* Set the X-Forwarded-For, X-Forwarded-Proto, and X-Forwarded-Host HTTP headers. * Set the X-Forwarded-For, X-Forwarded-Proto, and X-Forwarded-Host HTTP headers.