From f6600889c5fcb058e39949e2b230ae84ecad5b76 Mon Sep 17 00:00:00 2001 From: Luca Belluccini Date: Thu, 6 Mar 2025 13:05:27 +0100 Subject: [PATCH] Update fleet-agent-proxy-package-registry.asciidoc --- .../fleet-agent-proxy-package-registry.asciidoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/en/ingest-management/fleet-agent-proxy-package-registry.asciidoc b/docs/en/ingest-management/fleet-agent-proxy-package-registry.asciidoc index 68b54d360..34303b2e5 100644 --- a/docs/en/ingest-management/fleet-agent-proxy-package-registry.asciidoc +++ b/docs/en/ingest-management/fleet-agent-proxy-package-registry.asciidoc @@ -17,6 +17,10 @@ example: xpack.fleet.registryProxyUrl: your-nat-gateway.corp.net ---- +If your HTTP Proxy requires authentication, you can include the +credentials in the URI, such as `https://username:password@your-nat-gateway.corp.net`, +only when using HTTPS. + == What information is sent to the {package-registry}? In production environments, {kib}, through the {fleet} plugin, is the only service interacting with the {package-registry}. Communication happens when interacting with the Integrations UI, and when upgrading {kib}. The shared information is about discovery of Elastic packages and their available versions. In general, the only deployment-specific data that is shared is the {kib} version.