-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Make Kestrel Endpoints' "SslProtocols" settable via config #22663
Copy link
Copy link
Closed
Labels
DoneThis issue has been fixedThis issue has been fixedarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-kestrelhelp wantedUp for grabs. We would accept a PR to help resolve this issueUp for grabs. We would accept a PR to help resolve this issue
Milestone
Metadata
Metadata
Assignees
Labels
DoneThis issue has been fixedThis issue has been fixedarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-kestrelhelp wantedUp for grabs. We would accept a PR to help resolve this issueUp for grabs. We would accept a PR to help resolve this issue
Type
Fields
Give feedbackNo fields configured for issues without a type.
Is your feature request related to a problem? Please describe.
Given our recent changes to Kestrel's default supported TLS protocol versions, we should make "SslProtocols" settable via config, not just code as demonstrated in the announcement.
Describe the solution you'd like
Putting something like the following appsettings.json should configure "SslProtocols".
{ "Kestrel": { "EndpointDefaults": { "SslProtocols": [ "Tls11", "Tls12", "Tls13" ] }, "Endpoints": { "NamedHttpsEndpoint": { "Url": "https://localhost:6443", "SslProtocols": [ "Tls12", "Tls13" ] } } } }Additional context
#22437