diff --git a/aspnetcore/security/authentication/social/index.md b/aspnetcore/security/authentication/social/index.md index af96bb979b26..0722ba048504 100644 --- a/aspnetcore/security/authentication/social/index.md +++ b/aspnetcore/security/authentication/social/index.md @@ -1,19 +1,20 @@ --- title: Using external login providers with Identity in ASP.NET Core +ai-usage: ai-assisted author: wadepickett -description: Create an ASP.NET Core app using Identity with external authentication providers such as Facebook, Twitter, Google, and Microsoft. +description: Create an ASP.NET Core app using Identity with external authentication providers such as Facebook, X (formerly Twitter), Google, and Microsoft. ms.author: wpickett ms.custom: mvc, sfi-image-nochange -ms.date: 07/09/2025 +ms.date: 04/21/2026 uid: security/authentication/social/index --- # External provider authentication in ASP.NET Core Identity -By [Valeriy Novytskyy](https://github.com/01binary) and [Rick Anderson](https://twitter.com/RickAndMSFT) +By [Valeriy Novytskyy](https://github.com/01binary) and [Rick Anderson](https://x.com/RickAndMSFT) This article explains how to build an ASP.NET Core app that enables users to sign in using OAuth 2.0 with credentials from external authentication providers. -[Facebook](xref:security/authentication/facebook-logins), [Twitter](xref:security/authentication/twitter-logins), [Google](xref:security/authentication/google-logins), and [Microsoft](xref:security/authentication/microsoft-logins) providers are covered in the following sections and use the starter project created in this article. Other providers are available in third-party packages such as [OpenIddict](https://documentation.openiddict.com/integrations/web-providers), [AspNet.Security.OAuth.Providers](https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers) and [AspNet.Security.OpenId.Providers](https://github.com/aspnet-contrib/AspNet.Security.OpenId.Providers). +[Facebook](xref:security/authentication/facebook-logins), [X (formerly Twitter)](xref:security/authentication/twitter-logins), [Google](xref:security/authentication/google-logins), and [Microsoft](xref:security/authentication/microsoft-logins) providers are covered in the following sections and use the starter project created in this article. Other providers are available in third-party packages such as [OpenIddict](https://documentation.openiddict.com/integrations/web-providers), [AspNet.Security.OAuth.Providers](https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers) and [AspNet.Security.OpenId.Providers](https://github.com/aspnet-contrib/AspNet.Security.OpenId.Providers). Enabling users to sign in with their existing credentials is convenient for the users and shifts many of the complexities of managing the sign-in process onto a third party. @@ -21,8 +22,9 @@ Enabling users to sign in with their existing credentials is convenient for the # [Visual Studio](#tab/visual-studio) -* Select the **ASP.NET Core Web App** template. Select **OK**. -* In the **Authentication type** input, select **Individual Accounts**. +* Select the **ASP.NET Core Web App** template and select **Next**. +* Name the project and select **Next**. +* In the **Authentication type** dropdown, select **Individual Accounts** and select **Create**. # [Visual Studio Code / .NET CLI](#tab/visual-studio-code+net-cli) @@ -44,7 +46,7 @@ Enabling users to sign in with their existing credentials is convenient for the * The `dotnet new` command uses the `-o|--output` option to create a new Razor Pages project in the `WebApp1` folder. * `-au Individual` creates the code for Individual authentication. - * `-uld` uses LocalDB, a lightweight version of SQL Server Express for Windows. Omit `-uld` to use SQLite. + * `-uld` uses LocalDB, a lightweight version of SQL Server Express for Windows. Omit `-uld` to use SQLite, which is the default across all platforms. For more information, see [`dotnet new