daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update enforcing-ssl.md (#9231) 

Fixes #7351

I tested on a clean 2.2 Preview 3 machine and a 2.1 RTM
pull/9319/head
Rick Anderson 2018-10-29 14:48:50 -10:00 committed by GitHub
parent c824a8f947
commit a755bcb804
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
aspnetcore/security/enforcing-ssl.md
View File

@ -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).