2.2 KiB
| title | author | description | ms.author | ms.date | uid |
|---|---|---|---|---|---|
| Articles based on ASP.NET Core projects created with individual user accounts | rick-anderson | Discover articles based on ASP.NET Core projects created with individual user accounts. | riande | 11/30/2017 | security/authentication/individual |
Articles based on ASP.NET Core projects created with individual user accounts
ASP.NET Core Identity is included in project templates in Visual Studio with the "Individual User Accounts" option.
The authentication templates are available in .NET Core CLI with -au Individual:
::: moniker range=">= aspnetcore-2.1"
dotnet new mvc -au Individual
dotnet new webapi -au Individual
dotnet new webapp -au Individual
::: moniker-end
::: moniker range="= aspnetcore-2.0"
dotnet new mvc -au Individual
dotnet new webapi -au Individual
dotnet new razor -au Individual
::: moniker-end
No Authentication
Authentication is specified in the .NET Core CLI with the -au option. In Visual Studio, the Change Authentication dialog is available for new web applications. The default for new web apps in Visual Studio is No Authentication.
Projects created with no authentication:
- Don't contain web pages and UI to sign in and sign out.
- Don't contain authentication code.
Windows Authentication
Windows Authentication is specified for new web apps in the .NET Core CLI with the -au Windows option. In Visual Studio, the Change Authentication dialog provides the Windows Authentication options.
If Windows Authentication is selected, the app is configured to use the Windows Authentication IIS module. Windows Authentication is intended for Intranet web sites.
Additional resources
The following articles show how to use the code generated in ASP.NET Core templates that use individual user accounts: