Skip to main content

Part-3 Blazor Server Cookie Authentication

In this article, we are going to implement a 'User Login Page' in our Blazor Server application.

In this part of the article, we have to accomplish our targets like:
  • Login User Form.
  • Login Authentication Logic.
  • Configuring Cookie Authentication Service.
  • Installing Blazor Authorization Package 'Microsoft.AspNetCore.Components.Authorization'.
  • Adding the 'CascadingAuthenticationState' component.
  • Using the 'AuthorizeView' component.

Login Password Validation:

Let's add logic to validate the user entered password in the login form against the user hash password stored in the database.
Logic/AccountLogic:
private bool ValidatePasswordHash(string password, string dbPassword)
{
	byte[] dbPasswordHashBytes = Convert.FromBase64String(dbPassword);

	byte[] salt = new byte[16];
	Array.Copy(dbPasswordHashBytes, 0, salt, 0, 16);

	var userPasswordBytes = new Rfc2898DeriveBytes(password, salt, 1000);
	byte[] userPasswordHash = userPasswordBytes.GetBytes(20);

	for (int i = 0; i < 20; i++)
	{
		if (dbPasswordHashBytes[i + 16] != userPasswordHash[i])
		{
			return false;
		}
	}
	return true;
}
  • (Line: 1) The 'ValidatePasswordHash()' method 1st parameter 'password' value fetched the user entered in the login form and the 2nd parameter 'dbPassword'(Hashed password value) value fetched from the database.
  • (Line: 3) Fetching database password hash bytes of data from the string.
  • (Line: 5-6) Our Database hashed password value first 16 bytes are 'salt' key(Check password hash logic in Part-2), so let's fetch 'salt' key.
  • (Line: 8-9) Since hashing means one-way encryption, we can't decrypt the password value stored in the database. So here we will hash the password from the user login form with help of the 'Salt' key.
  • (Line: 11-17) Comparing the password hash byte values. If all bytes are the same password is valid else the user-entered password is invalid.

Implement User Login Logic:

Let's create a login form model like 'LoginVm.cs'.
Models/LoginVm.cs:
namespace Dot6.Bserver.Cookie.Auth.Models.Auth;

public class LoginVm
{
    public string Email { get; set; }
    public string Password { get; set; }
}
Let's add our logic for user authentication.
Logic/AccountLogic:
public async Task<string> UserLoginAsyn(LoginVm loginVm)
{
	Users user = await _myCookieAuthContext.Users
	.Where(_ => _.Email.ToLower() == loginVm.Email.ToLower())
	.FirstOrDefaultAsync();

	if (user == null)
	{
		return "Invalid Credentials";
	}

	if (!ValidatePasswordHash(loginVm.Password, user.PasswordHash))
	{
		return "Invalid Credentials";
	}

	var claims = new List<Claim>();
	claims.Add(new Claim(ClaimTypes.Name, $"{user.FirstName} {user.LastName}"));
	claims.Add(new Claim(ClaimTypes.Email, user.Email));

	var userRoles = await _myCookieAuthContext.UserRoles.Join(_myCookieAuthContext.Roles,
						ur => ur.RoleId,
						u => u.Id,
						(ur, u) => new { RoleId = ur.RoleId, RoleName = u.Name, UserId = ur.UserId }
					)
					.Where(_ => _.UserId == user.Id)
					.ToListAsync();

	foreach (var ur in userRoles)
	{
		claims.Add(new Claim(ClaimTypes.Role, ur.RoleName));
	}

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

	var authProperties = new AuthenticationProperties
	{ };

	await _accessor.HttpContext.SignInAsync(
	   CookieAuthenticationDefaults.AuthenticationScheme,
	   new ClaimsPrincipal(claimsIdentity),
	   authProperties);

	return string.Empty;
}
  • (Line: 3-5) Based on the user email address try to fetch user data from the database.
  • (Line: 12-15) Validating user-entered passwords against our database hash passwords.
  • (Line: 17-19) Adding user email and username as the authentication claims.
  • (Line: 21-27) Fetching user roles from the 'UserRoles' table.
  • (Line: 29-32) Adding the role claims.
  • (Line: 34-35) Initialized 'System.Security.Claims.ClaimsIdentity()' and passing claims and cookie authentication scheme name as the parameters.
  • (Line: 40-43) The 'SignInAsync()' method authenticates a user by creating the authentication cookie.
Let's add the login method definition into the 'IAccountLogic'.
Logic/IAccountLogic:
Task<string> UserLoginAsyn(LoginVm loginVm);

Create Login Razor Pages:

Let's create a user Login Razor Pages like 'Login.cshtml', 'Login.cshtml.cs' files.
Areas/Identity/Pages/Account/Login.cshtml.cs:
using Dot6.Bserver.Cookie.Auth.Models.Auth;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.RazorPages;

namespace Dot6.Bserver.Cookie.Auth.Areas.Identity.Pages.Account;

public class LoginModel : PageModel
{

    private readonly IHttpContextAccessor _accessor;
    private readonly IAccountLogic _accountLogic;
    public LoginModel(IHttpContextAccessor accessor, IAccountLogic accountLogic)
    {
        _accessor = accessor;
        _accountLogic = accountLogic;
    }
    [BindProperty]
    public LoginVm LoginVm { get; set; }
    public string ErrorMessage;
    public async Task<IActionResult> OnGetAsync()
    {
        if (_accessor.HttpContext.User.Identity.IsAuthenticated)
        {
            return Redirect("/");
        }
        return Page();
    }

    public async Task<IActionResult> OnPostAsync()
    {
        ErrorMessage = await _accountLogic.UserLoginAsyn(LoginVm);
        if (!string.IsNullOrEmpty(ErrorMessage))
        {
            return Page();
        }
        return Redirect("/");
    }

}
  • (Line: 12) Injected the 'IHttpContextAccessor' and 'IAccountLogic'.
  • (Line: 17-18) The 'LoginVm' is a login form model.
  • (Line: 19) The 'ErrorMessage' property to display login error messages.
  • (Line: 20-27) The 'OnGetAsync' method executed for the 'HTTP GET' request that loads the user login form.
  • (Line: 22-25) Restrict authenticated user from accessing the login page.
  • (Line: 29-37) The 'OnPostAsync' gets invoked on submitting the login form.
  • (Line: 31) Invoking the 'UserLoginAsync' method for validating user credentials.
Areas/Identity/Pages/Account/Login.csthml:
@page "/identity/account/login"
@model LoginModel


<div class="container">
    <div class="row text-center">
        <div class="col">
            @if (!string.IsNullOrEmpty(Model.ErrorMessage))
            {
                <div class="alert alert-danger" role="alert">
                    @Model.ErrorMessage
                </div>
            }

        </div>
    </div>
    <div class="row">
        <div class="col-md-6 offset-md-3">
            <form method="POST">
                <legend>User Login</legend>
                <div class="mb-3">
                    <label for="txtEmail" class="form-label">Email</label>
                    <input asp-for="LoginVm.Email" type="text" class="form-control" id="txtEmail" />
                </div>

                <div class="mb-3">
                    <label for="txtPassword" class="form-label">Password</label>
                    <input asp-for="LoginVm.Password" type="password" class="form-control" id="txtPassword" />
                </div>

                <button type="submit" class="btn btn-primary">Register</button>
            </form>
        </div>

    </div>
</div>

Authentication Cookie Configuration:

Now register cookie authentication service into the 'Program.cs'.
Program.cs:
builder.Services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme)
.AddCookie(options =>
{
    options.ExpireTimeSpan = TimeSpan.FromDays(20);
});
  • Here defined the authentication name as 'CookieAuthenticationDefaults.AuthenticationScheme'.
  • The 'ExpirationTimeSpan' controls how much time the authentication ticket stored in the cookie will remain valid from the point it is created. The expiration information is stored in the protected cookie ticket. Because of that, an expired cookie will be ignored even if it is passed to the server after the browser should have purged it.
Let's add the authorization and authentication middleware into the 'Program.cs' just after the 'app.UserRouting()' middleware.
Program.cs:
app.UseAuthentication();
app.UseAuthorization();

Install Blazor Authorization Package:

Package Manager:
Install-Package Microsoft.AspNetCore.Components.Authorization -Version 6.0.1

.Net CLI:
dotnet add package Microsoft.AspNetCore.Components.Authorization --version 6.0.1

CascadingAuthenticationState Component:

The blazor application can't access the HttpContext into the Blazor component. So to access the information about authenticated users into the blazor component we have to use the cascading property like 'AuthenticationState' property. So to read this 'AuthenticationState' property we have to add the 'CascadingAuthenticationState' component in the 'App.razor'.

Display User Info On Authentication:

Let's create a blazor component to display the authenticated user information.
Shared/LoginDisplay.razor:
<AuthorizeView>
    <Authorized>
        <a href="Identity/Account/Manage">Hello, @context.User.Identity?.Name!</a>
    </Authorized>
    <NotAuthorized>
        <a href="Identity/Account/Register">Register</a>
        <a href="Identity/Account/Login">Log in</a>
    </NotAuthorized>
</AuthorizeView>
  • The 'AuthorizeView' is a built-in component that helps to display the content condition based on user authentication and authorization. The 'AuthorizeView' component provides the 'context' through which we can fetch user authenticated information.
  • Here we are displaying the user name if authenticated else we will show 'Login', 'Registration' links
(1)Login & Registration links
(2)Login Form
(3) Login Cookie
(4) Display authenticated user info.

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping Up:

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

Refer:

Follow Me:

Comments

  1. Hi!
    Thank your for your guide. I'm wondering how to get the current user id?

    ReplyDelete

Post a Comment

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