From a755bcb8042fb3f3a8aee8b9061873a3422d0fa1 Mon Sep 17 00:00:00 2001 From: Rick Anderson Date: Mon, 29 Oct 2018 14:48:50 -1000 Subject: [PATCH] Update enforcing-ssl.md (#9231) Fixes #7351 I tested on a clean 2.2 Preview 3 machine and a 2.1 RTM --- aspnetcore/security/enforcing-ssl.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/aspnetcore/security/enforcing-ssl.md b/aspnetcore/security/enforcing-ssl.md index eaf62235b0..6adc2a727d 100644 --- a/aspnetcore/security/enforcing-ssl.md +++ b/aspnetcore/security/enforcing-ssl.md @@ -221,6 +221,31 @@ dotnet new webapp --no-https ::: moniker range=">= aspnetcore-2.1" +## Trust the ASP.NET Core HTTPS development certificate on Windows and macOS + +.NET Core SDK includes a HTTPS development certificate. The certificate is installed as part of the first-run experience. For example, `dotnet --info` produces output similar to the following: + +```text +ASP.NET Core +------------ +Successfully installed the ASP.NET Core HTTPS Development Certificate. +To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only). +For establishing trust on other platforms refer to the platform specific documentation. +For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054. +``` + +Installing the .NET Core SDK installs the ASP.NET Core HTTPS development certificate to the local user certificate store. The certificate has been installed, but it's not trusted. To trust the certificate perform the one-time step to run the dotnet `dev-certs` tool: + +```console +dotnet dev-certs https --trust +``` + +The following command provides help on the `dev-certs` tool: + +```console +dotnet dev-certs https --help +``` + ## How to set up a developer certificate for Docker See [this GitHub issue](https://github.com/aspnet/Docs/issues/6199).