Skip to content

Commit

Permalink
Docs: fix typo in OIDC tenant resolution
Browse files Browse the repository at this point in the history
  • Loading branch information
michalvavrik committed Mar 30, 2024
1 parent b3ede8e commit 4ff04bb
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Check warning on line 713 in docs/src/main/asciidoc/security-openid-connect-multitenancy.adoc

View workflow job for this annotation

GitHub Actions / Linting with Vale

[vale] reported by reviewdog 🐶 [Quarkus.TermsSuggestions] Depending on the context, consider using 'because' or 'while' rather than 'as'. Raw Output: {"message": "[Quarkus.TermsSuggestions] Depending on the context, consider using 'because' or 'while' rather than 'as'.", "location": {"path": "docs/src/main/asciidoc/security-openid-connect-multitenancy.adoc", "range": {"start": {"line": 713, "column": 9}}}, "severity": "INFO"}
<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.
Expand Down

0 comments on commit 4ff04bb

Please sign in to comment.