From c361cd155ba2f48dd5fc778fcab95709f0e45757 Mon Sep 17 00:00:00 2001 From: Karen Metts <35154725+karenzone@users.noreply.github.com> Date: Wed, 11 Jun 2025 17:37:05 -0400 Subject: [PATCH] Doc: Remove note about agent certificate for control plane traffic --- docs/en/ingest-management/fleet-agent-proxy-managed.asciidoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/en/ingest-management/fleet-agent-proxy-managed.asciidoc b/docs/en/ingest-management/fleet-agent-proxy-managed.asciidoc index aaee58bf8..e9eac2005 100644 --- a/docs/en/ingest-management/fleet-agent-proxy-managed.asciidoc +++ b/docs/en/ingest-management/fleet-agent-proxy-managed.asciidoc @@ -179,6 +179,4 @@ Equally important is the Certificate Authority that the agents need to use to va image::images/elastic-agent-edit-proxy-secure-settings.png[Screen capture of the Edit Proxy UI, highlighting the Certificate and Certificate key settings] -NOTE: Currently {agents} will not present a certificate for Control Plane traffic to the {fleet-server}. Some proxy servers are setup to mandate that the client setting up a connection presents a certificate to them before allowing that client to connect. This issue will be resolved by link:https://github.com/elastic/elastic-agent/issues/2248[issue #2248]. Our recommendation is to avoid adding a secure proxy as such in a {fleet-server} configuration flyout. - -NOTE: In case {kib} is behind a proxy server or is otherwise unable to access the {package-registry} to download package metadata and content, refer to <>. \ No newline at end of file +NOTE: In case {kib} is behind a proxy server or is otherwise unable to access the {package-registry} to download package metadata and content, refer to <>.