From 6a2b666f9d7e81ac03786750571651c21eef0c9a Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 11 Jul 2024 05:44:06 -0600 Subject: [PATCH] Update Docker & Kubernetes/Docker/Docker Compose/Keycloak.md --- Docker & Kubernetes/Docker/Docker Compose/Keycloak.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Docker & Kubernetes/Docker/Docker Compose/Keycloak.md b/Docker & Kubernetes/Docker/Docker Compose/Keycloak.md index ce25631..24ef4ec 100644 --- a/Docker & Kubernetes/Docker/Docker Compose/Keycloak.md +++ b/Docker & Kubernetes/Docker/Docker Compose/Keycloak.md @@ -123,7 +123,7 @@ At this point, we need to add the official Keycloak plugin to Traefik's main con ## Install Keycloak Plugin If you do not already have the following added to the end of your `command:` section of the docker-compose.yml file in Portainer, go ahead and add it: -``` yml +``` yaml # Keycloak plugin configuration - "--experimental.plugins.keycloakopenid.moduleName=github.com/Gwojda/keycloakopenid" - "--experimental.plugins.keycloakopenid.version=v0.1.34" @@ -154,13 +154,13 @@ At this point, within Keycloak, you need to configure domains that you are allow ## Adding Middleware to Dynamic Traefik Service Config Files At this point, you are in the final stretch, you just need to add the middleware to the Traefik dynamic config files to ensure that it routes the traffic to Keycloak when someone attempts to access that service. Put the following middleware section under the `routers:` section of the config file. -``` yml +``` yaml middlewares: - auth-bunny-lab-io # Referencing the Keycloak Server ``` A full example config file would look like the following: -``` yml +``` yaml http: routers: example: