From 48751f40cf958e938ce6f4f57659796883cf0c26 Mon Sep 17 00:00:00 2001 From: "aspire-repo-bot[bot]" <268009190+aspire-repo-bot[bot]@users.noreply.github.com> Date: Thu, 13 Aug 2026 20:46:57 +0000 Subject: [PATCH 1/2] docs: document TypeScript AppHost dev-cert trust for outbound TLS Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../src/content/docs/app-host/typescript-apphost.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/frontend/src/content/docs/app-host/typescript-apphost.mdx b/src/frontend/src/content/docs/app-host/typescript-apphost.mdx index 09e6b40f8..9b011c896 100644 --- a/src/frontend/src/content/docs/app-host/typescript-apphost.mdx +++ b/src/frontend/src/content/docs/app-host/typescript-apphost.mdx @@ -416,6 +416,12 @@ aspire certs trust ``` +### Trusting the certificate for outbound TLS connections + +When your AppHost code opens TLS connections to Aspire-managed resources at run time (for example, connecting directly to the dashboard's OTLP endpoint from custom AppHost logic), the Aspire CLI ensures Node.js trusts the same development certificate that DCP uses. The CLI exports the trusted development certificate into a content-addressed PEM cache under `ASPIRE_HOME`, and Node.js is configured to trust that bundle through the `NODE_EXTRA_CA_CERTS` environment variable. + +If you've already set `NODE_EXTRA_CA_CERTS` for your own certificates, the CLI preserves your value by generating a combined bundle that includes both your certificates and the Aspire development certificate, rather than overwriting your setting. + See [Certificate configuration](/app-host/certificate-configuration/) for details on HTTPS certificate management in Aspire, including Linux-specific setup. From 503ddd4d4e98bee145566828748c40366568332e Mon Sep 17 00:00:00 2001 From: David Pine Date: Fri, 14 Aug 2026 19:00:24 -0500 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- src/frontend/src/content/docs/app-host/typescript-apphost.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/frontend/src/content/docs/app-host/typescript-apphost.mdx b/src/frontend/src/content/docs/app-host/typescript-apphost.mdx index 9b011c896..f1c358b58 100644 --- a/src/frontend/src/content/docs/app-host/typescript-apphost.mdx +++ b/src/frontend/src/content/docs/app-host/typescript-apphost.mdx @@ -418,7 +418,7 @@ aspire certs trust ### Trusting the certificate for outbound TLS connections -When your AppHost code opens TLS connections to Aspire-managed resources at run time (for example, connecting directly to the dashboard's OTLP endpoint from custom AppHost logic), the Aspire CLI ensures Node.js trusts the same development certificate that DCP uses. The CLI exports the trusted development certificate into a content-addressed PEM cache under `ASPIRE_HOME`, and Node.js is configured to trust that bundle through the `NODE_EXTRA_CA_CERTS` environment variable. +When your AppHost code opens TLS connections to Aspire-managed resources at runtime (for example, connecting directly to the dashboard's OTLP endpoint from custom AppHost logic), the Aspire CLI ensures Node.js trusts the same development certificate that the Developer Control Plane (DCP) uses. The CLI exports the trusted development certificate into a content-addressed PEM cache under the Aspire home directory (`ASPIRE_HOME`), and Node.js is configured to trust that bundle through the `NODE_EXTRA_CA_CERTS` environment variable. If you've already set `NODE_EXTRA_CA_CERTS` for your own certificates, the CLI preserves your value by generating a combined bundle that includes both your certificates and the Aspire development certificate, rather than overwriting your setting.