From 51c9d1e6c3405cd8cf81754cab378ac903d0f72f Mon Sep 17 00:00:00 2001 From: Paul Banks Date: Thu, 20 May 2021 16:28:38 +0100 Subject: [PATCH] Fix doc note since we switched authorization mechanism in 1.9 (#10266) --- website/content/docs/connect/proxies/envoy.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/connect/proxies/envoy.mdx b/website/content/docs/connect/proxies/envoy.mdx index 5aa5dc6eb8..9b2a2ec240 100644 --- a/website/content/docs/connect/proxies/envoy.mdx +++ b/website/content/docs/connect/proxies/envoy.mdx @@ -497,9 +497,9 @@ definition](/docs/connect/registration/service-registration) or overridden by the Connect TLS certificates and validation context. This means there is no way to override Connect's mutual TLS for the public listener. - - Every `FilterChain` will have the `envoy.ext_authz` filter prepended to the - filters array to ensure that all inbound connections are authorized by - Connect. + - Every `FilterChain` will have the `envoy.filters.{network|http}.rbac` filter + prepended to the filters array to ensure that all inbound connections are + authorized by Connect. Before Consul 1.9.0 `envoy.ext_authz` was inserted instead. - `envoy_local_cluster_json` - Specifies a complete [Envoy cluster](https://www.envoyproxy.io/docs/envoy/v1.10.0/api-v2/api/v2/cds.proto#cluster) to be delivered in place of the local application cluster. This allows