status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Docs and changelog edits 

Signed-off-by: Mark Anderson <manderson@hashicorp.com>
This commit is contained in:
Mark Anderson 2022-05-02 09:35:34 -07:00
parent fee6c7a7b6
commit 05dc5a26b7
3 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.changelog/12878.txt
View File

@ -1,3 +1,3 @@
```release-note:improvement
agent: Envoy now inserts x-forwarded-client-cert for incoming proxy connections
```
xds: Envoy now inserts x-forwarded-client-cert for incoming proxy connections
```

4
agent/structs/config_entry_mesh.go
View File

@ -44,6 +44,10 @@ type MeshDirectionalTLSConfig struct {
CipherSuites []types.TLSCipherSuite `json:",omitempty" alias:"cipher_suites"`
}
type MeshHTTPConfig struct {
SanitizeXForwardedClientCert bool `alias:"sanitize_x_forwarded_client_cert"`
}
func (e *MeshConfigEntry) GetKind() string {
return MeshConfig
}

5
website/content/docs/connect/config-entries/mesh.mdx
View File

@ -368,8 +368,9 @@ Note that the Kubernetes example does not include a `partition` field. Configura
name: 'SanitizeXForwardedClientCert',
yaml: false,
type: 'bool: <optional>',
description: `Set the envoy forwardClientCertDetails to SANITIZE everywhere. Ordinarily Consul will configure Envoy to
insert x-forwarded-client-cert headers where appropriate. This returns Consul to the pre 1.12.1 behavior`,
description: `Set the envoy \`forward_client_cert_details\` option to \`SANITIZE\` for all proxies. This
configures Envoy to not send the \`x-forwarded-client-cert\` header to the next hop. If
unspecified or \`false\`, the XFCC header is propagated to upstream applications.`,
},
],
},