Skip to main content

Part-2 Blazor WebAssembly Cookie Authentication With Facebook

In this article, we are going to implement Blazor WebAssembly cookie authentication with Facebook(external login provider).

Click here for - Part-1 Blazor WebAssembly authentication with .net core cookie.

Install Facebook NuGet In API Project:

Let's install the Microsoft Facebook Authentication package.
.NET CLI Command:
dotnet add package Microsoft.AspNetCore.Authentication.Facebook --version 6.0.3

Package Manager:
Install-Package Microsoft.AspNetCore.Authentication.Facebook -Version 6.0.3

Register API Wih Facebook:

To enable Facebook authentication we have to register our API project with Facebook. So following are facebook registration steps.

Step1:
Go to the Facebook Developer page at "https://developers.facebook.com/apps/".

Step2:
Go to the 'My Apps' menu and click on the 'Create App' button.

Step3:
In the 'Create An App' section, choose the 'Consumer' option and then click on the 'Next' button.

Step4:
In the 'Details' form, give a 'Display Name' and then click the 'Create App' button.

Step5:
On 'Add products to your app', click on the 'Setup' button on the 'Facebook Login' page.

Step 6:
The 'Facebook Login' menu is on the left-hand side, under it select the 'Settings' tab.

Step 7:
On 'Client OAuth Settings', add the 'Valid OAuth Redirect URLs' like '{domain}/signin-facebook'. Here 'signin-facebook' path is the default redirection path for the facebook provider.

Step 8:
Now left-side menu 'Settings' then select 'Basic' option, Here we 2 keys we need to configure into our API project like 'App ID', 'App Secret'.

Add Facebook Settings To API Project:

In our API project into the 'appsettings.Development.json' let's add our Facebook settings like 'AppId', and 'AppSecret'.
API_Project/appsettings.Development.json:
"FacebookSettings":{
  "AppID":"00000000",
  "AppSecret":"0000000"
}

Register Facebook Service In API Project:

Now register the Facebook service into the API project.
API_Project/Program.cs:
builder.Services.AddAuthentication(
    CookieAuthenticationDefaults.AuthenticationScheme
)
.AddCookie()
.AddFacebook(fb => {
    fb.AppId = builder.Configuration
    .GetSection("FacebookSettings").GetValue<string>("AppID");
    
    fb.AppSecret = builder.Configuration
    .GetSection("FacebookSettings").GetValue<string>("AppSecret");
});
  • (Line: 5-11) Register the 'AddFacebook' service and then configure 'AppId', 'AppSecret' into it.

Implement Facebook Authentication Logic In API Project:

Let's implement a private method that contains logic to fetch or create the user into our database while trying to authenticate with the external logins like 'Facebook', 'Google', 'Twitter', 'Microsoft' etc.
API_Project/Controllers/AuthController.cs:
private async Task<User> ManageExternalLoginUser(string email,
string firstName,
string lastName,
string externalLoginName)
{
	var user = await _cookieAuthContext
	.User.Where(_ => _.Email.ToLower() == email.ToLower()
	&& _.ExternalLoginName.ToLower() == externalLoginName.ToLower())
	.FirstOrDefaultAsync();

	if (user != null)
	{
		return user;
	}

	var newUser = new User
	{
		Email = email,
		ExternalLoginName = externalLoginName,
		FirstName = firstName,
		LastName = lastName
	};
	_cookieAuthContext.User.Add(newUser);
	await _cookieAuthContext.SaveChangesAsync();
	return newUser;
}
  • (Line: 1-4) The 'ManageExternalLoginUser' method contains input parameter like 'email', 'firstName', 'lastName', 'externalLoginName'. These input parameter are taken from the Facebook claims which we are going to fetch or create an user into the database.
  • (Line: 6-9) Fetching Facebook login user information from our database if we already stored them.
  • (Line: 16-24) If the Facebook user information does not exist in our database, then we need to save it as a new user.
Once we try to sign-in with a Facebook then the user context and auth cookie are created by default while reaching our callback action method('FacebookLoginCallback' a callback action method will implement in upcoming steps). So from this user context, we will read user claims then we fetch or save them into the database using 'ManageExternalLoginUser()'(method implemented in the previous step). So once we fetch our own user information from the database we need to remove the default user context and the auth cookie and then we have to create a new context and new auth cookie as below.
API_Project/Controllers/AuthController.cs:
private async Task RefreshExternalSignIn(User user)
{
	var claims = new List<Claim>
	{
		new Claim("userid", user.Id.ToString()),
		new Claim(ClaimTypes.Email, user.Email)
	};

	var claimsIdentity = new ClaimsIdentity(
		claims, CookieAuthenticationDefaults.AuthenticationScheme);

	var authProperties = new AuthenticationProperties();

	HttpContext.User.AddIdentity(claimsIdentity);

	await HttpContext.SignOutAsync();

	await HttpContext.SignInAsync(
		CookieAuthenticationDefaults.AuthenticationScheme,
		new ClaimsPrincipal(claimsIdentity),
		authProperties);
}
  • (Line: 3-7) Creating a collection of claims from our user information.
  • (Line: 9-10) Initialized ClaimsIdentity object.
  • (Line: 14) Updating the user context with a new claims identity.
  • (Line: 16) SignOut from the default cookie.
  • (Line: 18-21) Creating a new Sign-In cookie with our own user claims.
Now let's implement the 'FacebookLogin' action method.
API_Project/Controllers/AuthController.cs:
[HttpGet]
[Route("facebook-login")]
public IActionResult FacebookLogin(string returnURL)
{
	return Challenge(
		new AuthenticationProperties()
		{
			RedirectUri = Url.Action(nameof(FacebookLoginCallback), new { returnURL })
		},
		FacebookDefaults.AuthenticationScheme
	);
}
  • (Line: 3) Here 'returnURL' query parameter will be our Blazor WebAssembly application URL.
  • (Line: 5-11) The 'Challenge' method is to invoke the external authentication provider like 'Facebook'.
  • (Line: 8) After successful authentication, the external provider will be redirected to our 'FacebookLoginCallbak' action method(which we will implement in the next step).
  • (Line: 10) The 'Challenge()' method is a generic method so we have to specify the external authentication scheme like 'FacebookDefaults.AuthenticationScheme'.
After successful authentication with Facebook, then it will be redirected to the 'FacebookLoginCallback' method.
API_Project/Controllers/AuthController.cs:
[HttpGet]
[Route("facebook-login-callback")]
public async Task<IActionResult> FacebookLoginCallback(string returnURL)
{
	var authenticationResult = await HttpContext
	.AuthenticateAsync(FacebookDefaults.AuthenticationScheme);
	if (authenticationResult.Succeeded)
	{
		string email = HttpContext
		.User.Claims.Where(_ => _.Type == ClaimTypes.Email)
		.Select(_ => _.Value)
		.FirstOrDefault();

		string firstName = HttpContext
		.User.Claims.Where(_ => _.Type == ClaimTypes.Name)
		.Select(_ => _.Value)
		.FirstOrDefault();

		string lastName = HttpContext
		.User.Claims.Where(_ => _.Type == ClaimTypes.Surname)
		.Select(_ => _.Value)
		.FirstOrDefault();

		var user = await ManageExternalLoginUser(
			email,
			firstName,
			lastName,
			"Facebook"
		);

		await RefreshExternalSignIn(user);
        return Redirect($"{returnURL}?externalauth=true");
	}
	return Redirect($"{returnURL}?externalauth=false");
}
  • (Line: 3) The 'returnURL' is our Blazor WebAssembly URL.
  • (Line: 5-6) Fetch the Facebook authentication status from the HttpContext.
  • (Line: 7)Checks for the Facebook success status.
  • (Line: 9-22) Fetching Facebook claims like 'email', 'name', 'surname'.
  • (Line: 24-29) Invoking the 'ManageExternalLoginUser' method. This method creates a user that doesn't exist in the database and then returns the user as output.
  • (Line: 31) Invoking the 'RefreshExternalSignIn()' method.
  • (Line: 32) Redirecting to our Blazor WebAssembly application with query parameters like 'externalauth= true', this query parameter will be used by the Blazor WebAssembly application to set 'isauthenticated' local storage variable.
  • (Line: 34) Redirecting to the Blazor WebAssembly application with parameters like 'externalauth=false', this query parameter notifies the Blazor WebAssembly application that Facebook authentication failed.

Update 'isauthenticated' Local Storage Variable On Success OF Facebook Authentication In Blazor App:

Recall Part-1 on successful .net core cookie authentication we have stored local storage variable 'isauthenticated'. Similarly, we have to do it for any external login provider authentication also.
BlazorWasm_Project/App.razor:(Code Part)
 
private async Task OnNavigateAsync(NavigationContext args)
{
	var auth = await _localStorageService.GetItemAsync<string>("isauthenticated");
	if (string.IsNullOrEmpty(auth) && args.Path.ToLower().Contains("externalauth=true"))
	{
		auth = "true";
		await _localStorageService.SetItemAsStringAsync("isauthenticated","true");
	}
	var user = (await (_authStateProvider as CustomAuthStateProvider)
	.GetAuthenticationStateAsync()).User;

	if (!string.IsNullOrEmpty(auth) && !user.Identity.IsAuthenticated)
	{
		var response = await _apiLogic.UserProfileAsync();
		if (response.Message == "Success")
		{
			(_authStateProvider as CustomAuthStateProvider)
			.SetAuthInfo(response.UserProfile);
		}
		else if (response.Message == "Unauthorized")
		{
			await _localStorageService.RemoveItemAsync("isauthenticated");
		}
	}
}
  • (Line: 5-9) Checking for 'externalauth=true' query parameter that represents the external login provider is successful, then we have to set the 'isauthenticated' local storage variable.

Add Facebook Link On Login.razor In Blazor WebAssembly App:

Now add a Facebook link or button in the Login.razor component.
Blazor_Wasm/Pages/Login.razor:
<div class="row">
    <div class="col-md-6 offset-md-3">
        <div>
            <a href="https://localhost:7235/auth/facebook-login?returnurl=https://localhost:7218/"
            class="nav-link btn btn-link">
            Facebook
            </a>
        </div>
    </div>
</div>
  • Here URL is our Facebook API endpoint and the query parameter is our Blazor WebAssembly application URL
Step 1:

Step2:

Step3:

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

Hopefully, I think this article delivered some useful information about Blazor WebAssembly Cookie Authentication. using I love to have your feedback, suggestions, and better techniques in the comment section below.

Refer:

Follow Me:

Comments

Popular posts from this blog

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl

Usage Of CancellationToken In Asp.Net Core Applications

When To Use CancellationToken?: In a web application request abortion or orphan, requests are quite common. On users disconnected by network interruption or navigating between multiple pages before proper response or closing of the browser, tabs make the request aborted or orphan. An orphan request can't deliver a response to the client, but it will execute all steps(like database calls, HTTP calls, etc) at the server. Complete execution of an orphan request at the server might not be a problem generally if at all requests need to work on time taking a job at the server in those cases might be nice to terminate the execution immediately. So CancellationToken can be used to terminate a request execution at the server immediately once the request is aborted or orphan. Here we are going to see some sample code snippets about implementing a CancellationToken for Entity FrameworkCore, Dapper ORM, and HttpClient calls in Asp.NetCore MVC application. Note: The sample codes I will show in

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

NestJS File Upload

In this article, we are going to understand the steps to create a file uploading endpoint in the NestJS application. Key Features In NestJS File Upload: Let us know some key features of NestJS file upload before implementing a sample application. FileInterceptor: The 'FileInterceptor' will be decorated on top of the file upload endpoint. This interceptor will read single file data from the form posted to the endpoint. export declare function FilesInterceptor(fieldName: string, localOptions?: MulterOptions): Type<NestInterceptor>; Here we can observe the 'fieldName' first input parameter this value should be a match with our 'name' attribute value on the form file input field. So our interceptor read our files that are attached to the file input field. Another input parameter of 'MulterOptions' that provides configuration like file destination path, customizing file name, etc. FilesInterceptor: The 'FilesInterceptor' will be decorated on t