5.6 KiB

Raw Blame History

title	author	description	ms.author	ms.custom	ms.date	uid
Facebook and Google authentication in ASP.NET Core	rick-anderson	Create an ASP.NET Core app using OAuth 2.0 with external authentication providers such as Facebook, Twitter, Google, and Microsoft.	riande	mvc	03/07/2022	security/authentication/social/index

Facebook, Google, and external provider authentication in ASP.NET Core

By Valeriy Novytskyy and Rick Anderson

This tutorial demonstrates 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, Twitter, Google, and Microsoft 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, AspNet.Security.OAuth.Providers and AspNet.Security.OpenId.Providers.

Enabling users to sign in with their existing credentials:

Is convenient for the users.
Shifts many of the complexities of managing the sign-in process onto a third party.

Create a New ASP.NET Core Project

Visual Studio

Select the ASP.NET Core Web App template. Select OK.
In the Authentication type input, select Individual Accounts.

Visual Studio Code / Visual Studio for Mac

Open the terminal. For Visual Studio Code you can open the integrated terminal.
Change directories (cd) to a folder which will contain the project.
For Windows, run the following command:
```
dotnet new webapp -o WebApp1 -au Individual -uld
```
For macOS and Linux, run the following command:
```
dotnet new webapp -o WebApp1 -au Individual
```
- The dotnet new command creates 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.
- The code command opens the WebApp1 folder in a new instance of Visual Studio Code.

Apply migrations

Run the app and select the Register link.
Enter the email and password for the new account, and then select Register.
Follow the instructions to apply migrations.

[!INCLUDEForward request information when behind a proxy or load balancer section]

Social login providers assign Application Id and Application Secret tokens during the registration process. The exact token names vary by provider. These tokens represent the credentials your app uses to access their API. The tokens constitute the "user secrets" that can be linked to your app configuration with the help of Secret Manager. User secrets are a more secure alternative to storing the tokens in a configuration file, such as appsettings.json.

[!IMPORTANT] Secret Manager is for development purposes only. You can store and protect Azure test and production secrets with the Azure Key Vault configuration provider.

Follow the steps in Safe storage of app secrets in development in ASP.NET Core topic to store tokens assigned by each login provider below.

Use the following topics to configure your application to use the respective providers:

Facebook instructions
Twitter instructions
Google instructions
Microsoft instructions
Other provider instructions

[!INCLUDE]

Optionally set password

When you register with an external login provider, you don't have a password registered with the app. This alleviates you from creating and remembering a password for the site, but it also makes you dependent on the external login provider. If the external login provider is unavailable, you won't be able to sign in to the web site.

To create a password and sign in using your email that you set during the sign in process with external providers:

Select the Hello <email alias> link at the top-right corner to navigate to the Manage view.

Select Create

Set a valid password and you can use this to sign in with your email.

Additional information

Sign in with Apple Example Integration
See this GitHub issue for information on how to customize the login buttons.
Persist additional data about the user and their access and refresh tokens. For more information, see xref:security/authentication/social/additional-claims.

5.6 KiB Raw Blame History