-
Notifications
You must be signed in to change notification settings - Fork 527
Bind Kestrel options to config by default #1703
Comments
👀 |
Or you can name your endpoints: "Kestrel": {
"Endpoints": {
"CertFromStore": {
"Address": "localhost",
"Port": "44316",
"Certificate": { // Implies HTTPS
"Subject": "danroth27.com", // Pick the cert that matches the subject name with the latest expiry
"StoreName": "My",
"StoreLocation": "CurrentUser"
}
},
"LocalhostWithPort": {
"Address": "localhost",
"Port": "8080"
},
"CertFromFile": {
"Address": "localhost",
"Port": "44317",
"Certificate": {
"Path": "./mysslcert.pfx",
"Password": "abc!123" // In user secrets: Kestrel:Endpoints:CertFromFile:Certificate:Password
}
}
}
} |
This issue was moved to aspnet/MetaPackages#30 |
@danroth27 Did this change after MSBuild 2017. I've been trying the exact same setup and I can't get it to work. Tried in the following environments: Mac OS X - dotnet version 2.1.0-preview1-006919 Could you please point us in the right direction on how to use this properly. The docs at https://docs.microsoft.com/en-us/aspnet/core/security/https describe the exact same setup, but that article is from May, the same time as MSBuild2017 when you presented this feature. Steps to reproduce:
create
Logs Thank you! |
This feature was cut from 2.0.0. #1886 (comment) |
@natemcmaster thank you! I guess this should be updated. https://docs.microsoft.com/en-us/aspnet/core/security/https |
We will :) We're working on getting our docs ready for 2.0 RTM. dotnet/AspNetCore.Docs#3815 |
Since config is in DI now by default we should support binding the Kestrel options to config by default (for
UseKestrel()
).The text was updated successfully, but these errors were encountered: