From 4ff04bbf6768d9fbc8c13f9b5dcc444e03ba65ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michal=20Vav=C5=99=C3=ADk?= Date: Sat, 30 Mar 2024 11:43:46 +0100 Subject: [PATCH] Docs: fix typo in OIDC tenant resolution --- .../main/asciidoc/security-openid-connect-multitenancy.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/security-openid-connect-multitenancy.adoc b/docs/src/main/asciidoc/security-openid-connect-multitenancy.adoc index 7506ef803694d..eacb699bcbf9f 100644 --- a/docs/src/main/asciidoc/security-openid-connect-multitenancy.adoc +++ b/docs/src/main/asciidoc/security-openid-connect-multitenancy.adoc @@ -707,8 +707,8 @@ Here is how you can select the `hr` tenant for the `sayHello` endpoint of the `H [source,properties] ---- quarkus.oidc.hr.tenant-paths=/api/hello <1> -quarkus.oidc.google.tenant-paths=/api/* <2> -quarkus.oidc.google.tenant-paths=/*/hello <3> +quarkus.oidc.a.tenant-paths=/api/* <2> +quarkus.oidc.b.tenant-paths=/*/hello <3> ---- <1> Same path-matching rules apply as for the `quarkus.http.auth.permission.authenticated.paths=/api/hello` configuration property from the previous example. <2> The wildcard placed at the end of the path represents any number of path segments. However the path is less specific than the `/api/hello`, therefore the `hr` tenant will be used to secure the `sayHello` endpoint.