-> dotnet dev-certs https generates certificates that are affected by the issue described on https://github.com/openssl/openssl/issues/1418 and https://github.com/dotnet/aspnetcore/issues/7246:
$ openssl verify localhost.crt CN = localhost error 20 at 0 depth lookup: unable to get local issuer certificate error localhost.crt: verification failed
-> due to that it’s impossible to have a dotnet client trust the certificate
[req] default_bits = 2048 default_keyfile = localhost.key distinguished_name = req_distinguished_name req_extensions = req_ext x509_extensions = v3_ca [req_distinguished_name] commonName = Common Name (e.g. server FQDN or YOUR name) commonName_default = localhost commonName_max = 64 [req_ext] subjectAltName = @alt_names [v3_ca] subjectAltName = @alt_names basicConstraints = critical, CA:false keyUsage = keyCertSign, cRLSign, digitalSignature,keyEncipherment [alt_names] DNS.1 = localhost DNS.2
CN = localhost error 18 at 0 depth lookup: self signed certificate error localhost.crt: verification failed
$ openssl verify localhost.crt localhost.crt: OK
"Kestrel": { "Certificates": { "Default": { "Path": "localhost.pfx", "Password": "" } } }
Work with our skilled .Net developers to accelerate your project and boost its performance.
Hire .Net Developers