You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/app-host/certificate-trust.md
+40-19Lines changed: 40 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,9 @@ ai-usage: ai-assisted
9
9
10
10
In Aspire, you can customize which certificates resources consider trusted for TLS/HTTPS traffic. This is particularly useful for resources that don't use the system's root trusted certificates by default, such as containerized applications, Python apps, and Node.js apps. By configuring certificate trust, you enable these resources to communicate securely with services that use certificates they wouldn't otherwise trust, including the Aspire dashboard's OTLP endpoint.
11
11
12
+
> [!IMPORTANT]
13
+
> Certificate trust customization only applies at run time. Custom certificates aren't included in publish or deployment artifacts.
14
+
12
15
## When to use certificate trust customization
13
16
14
17
Certificate trust customization is valuable when:
@@ -34,11 +37,11 @@ var builder = DistributedApplication.CreateBuilder(args);
34
37
35
38
// Explicitly enable development certificate trust
@@ -75,7 +78,15 @@ In the preceding example, the certificate bundle is created with custom certific
75
78
76
79
Certificate trust scopes control how custom certificates interact with a resource's default trusted certificates. Different scopes provide flexibility in managing certificate trust based on your application's requirements.
77
80
78
-
The `WithCertificateTrustScope` API accepts a <xref:Aspire.Hosting.ApplicationModel.CertificateTrustScope> value to specify the trust behavior:
81
+
The `WithCertificateTrustScope` API accepts a <xref:Aspire.Hosting.ApplicationModel.CertificateTrustScope> value to specify the trust behavior.
82
+
83
+
### Default trust scopes
84
+
85
+
Different resource types have different default trust scopes:
86
+
87
+
-**Append**: The default for most resources, appending custom certificates to the default trusted certificates.
88
+
-**System**: The default for Python projects, which combines custom certificates with system root certificates because Python doesn't properly support Append mode.
89
+
-**None**: The default for .NET projects on Windows, as there's no way to automatically change the default system store source.
79
90
80
91
### Append mode
81
92
@@ -148,14 +159,16 @@ Use `WithExecutableCertificateTrustCallback` to customize certificate trust for
// Override the path to default individual certificates in the container (this is a list of common certificate paths for various Linux distros by default)
190
+
// This should only need to be updated if your container has certificates in non-standard paths
0 commit comments