From b41a7749658c0dd42f444caa61c5703204668f95 Mon Sep 17 00:00:00 2001 From: jm96441n Date: Thu, 29 Jun 2023 16:15:27 +0000 Subject: [PATCH] backport of commit 807c08009129b98c75a01e7d6b2110840a43f824 --- website/content/docs/connect/intentions/jwt-authorization.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/intentions/jwt-authorization.mdx b/website/content/docs/connect/intentions/jwt-authorization.mdx index 9a8458054ea2..c49ac4fbc6e9 100644 --- a/website/content/docs/connect/intentions/jwt-authorization.mdx +++ b/website/content/docs/connect/intentions/jwt-authorization.mdx @@ -92,7 +92,7 @@ JWT = { } ``` -You can include additional configuration information to require the token to match specific claims. You can also configure the `JWT` field to apply only to requests that come from certain HTTP paths. Refer to [JWT validations with intentions](/consul/docs/conntect/config-entries/service-intentions#jwt-validations-with-intentions) for an example configuration. +You can include additional configuration information to require the token to match specific claims. You can also configure the `JWT` field to apply only to requests that come from certain HTTP paths. Refer to [JWT validations with intentions](/consul/docs/connect/config-entries/service-intentions#jwt-validations-with-intentions) for an example configuration. After you update the service intention, write the configuration to Consul so that it takes effect: