Skip to main content

Part-2 Blazor Server Cookie Authentication

In this article, we are going to implement User Registration logic in the Blazor Server application.

In this part of the article, we have to accomplish our targets like:
  • User Registration Form.
  • Password Hashing
  • User Registration Logic.
Click here for part-1

Create Asp.Net Core Areas Folder:

We are going to create Razor Pages for our User Registration, so let store them in the 'Areas' folder. So let's create 'Areas' folders and also add the 'Layout' template and a few other additional configurations.

Now let's create folders into our application like 'Areas\Identity\Pages\Account', 'Areas\Identity\Pages\Shared'.

Let's create a new layout for the pages inside of the 'Areas' folder. Let's create the layout file '_Layout.cshtml'.
<!DOCTYPE html>
<html lang="en">
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <link rel="stylesheet" href="/css/bootstrap/bootstrap.min.css" />
    <nav class="navbar navbar-dark bg-primary">
        <div class="container-fluid">
            <span class="navbar-brand mb-0 h1">Navbar</span>
Let's create a new '_ViewImports.cshtml' file into the 'Areas' to register the razor tag helper and then to register the namespaces.
@using Dot6.Bserver.Cookie.Auth.Areas.Identity.Pages.Account
@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
Let's create a new '_ViewStart.cshtml' file into the 'Areas' in which will specify the path to our newly created layout.
    Layout = "/Areas/Identity/Pages/Shared/_Layout.cshtml";

Create Registration From Model:

Now let's create a model for form binding like 'Models/Auth/RegiserVm.cs'.
namespace Dot6.Bserver.Cookie.Auth.Models.Auth;
public class RegisterVm
    public string FirstName { get; set; }
    public string LastName { get; set; }
    public string Email { get; set; }
    public string Password { get; set; }
    public string ConfirmPassword { get; set; }

Implement User Registration Logic:

Let's implement 'User Registration' logic, so lets create files like 'AccountLogic', 'IAccountLogic'.
public interface IAccountLogic
using Dot6.Bserver.Cookie.Auth.Data;

namespace Dot6.Bserver.Cookie.Auth.Logic;

public class AccountLogic : IAccountLogic
    private readonly MyCookieAuthContext _myCookieAuthContext;
    private readonly IHttpContextAccessor _accessor;

    public AccountLogic(MyCookieAuthContext myCookieAuthContext,
    IHttpContextAccessor accessor)
        _myCookieAuthContext = myCookieAuthContext;
        _accessor = accessor;
  • Here injected 'MyCookieAuthContext' and 'IHttpContextAcessor'.
Register our  'IHttpContextAccessor','IAccountLogic', 'AccountLogic' into the 'Program.cs'.
builder.Services.AddScoped<IAccountLogic, AccountLogic>();
Let's add logic for validating our user registration model.
using System.Text.RegularExpressions;

private string ResigstrationValidations(RegisterVm registerVm)
	if (string.IsNullOrEmpty(registerVm.Email))
		return "Eamil can't be empty";

	string emailRules = @"[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*@(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?";
	if (!Regex.IsMatch(registerVm.Email, emailRules))
		return "Not a valid email";

	if (_myCookieAuthContext.Users.Any(_ => _.Email.ToLower() == registerVm.Email.ToLower()))
		return "user already exists";

	if (string.IsNullOrEmpty(registerVm.Password)
		|| string.IsNullOrEmpty(registerVm.ConfirmPassword))
		return "Password Or ConfirmPasswor Can't be empty";

	if (registerVm.Password != registerVm.ConfirmPassword)
		return "Invalid confirm password";

	// atleast one lower case letter
	// atleast one upper case letter
	// atleast one special character
	// atleast one number
	// atleast 8 character length
	string passwordRules = @"^.*(?=.{8,})(?=.*\d)(?=.*[a-z])(?=.*[A-Z])(?=.*[!*@#$%^&+=]).*$";
	if (!Regex.IsMatch(registerVm.Password, passwordRules))
		return "Not a valid password";
	return string.Empty;
  • (Line: 5-8) Checking user email address empty or not.
  • (Line: 10-14) Email validation pattern check.
  • (Line: 16-19) Checking email against the database to confirm the user is already registered or not.
  • (Line: 21-25) Checking 'Password' or 'ConfirmPassword' empty or not.
  • (Line: 27-30) Verifying the 'Password' and 'ConfirmPassword' matching or not.
  • (Line: 32-41) Password validation pattern check.
Password is a security key for user authentication. It is a basic rule that never stores the plain password into the tables directly. So always recommend applying hashing on passwords. Hashing means oneway encryption which means value can't be decrypted. So let's add our password hashing logic.
private string PasswordHash(string password)
	byte[] salt = new byte[16];
	new RNGCryptoServiceProvider().GetBytes(salt);

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

	byte[] hashBytes = new byte[36];
	Array.Copy(salt, 0, hashBytes, 0, 16);
	Array.Copy(hash, 0, hashBytes, 16, 20);

	return Convert.ToBase64String(hashBytes);
  • (Line: 3) Initialized 16-byte array variable to store salt key for password hashing.
  • (Line: 4) Using 'System.Security.Cryptography.RNGCryptoServiceProvider' generating random salt key value.
  • (Line: 6) Using 'System.Security.Cryptography.Rfc2898DeriveBytes()' we hashing our passing by using our salt. Here value '1000' represents the iteration count for encrypting our password.
  • (Line: 7) Taking 20 bytes of data as our password byte value.
  • (Line: 9-13) Here we can observe that our salt value and password byte value are concatenated and stored as finally generated password hash.
Let's add our main method for our user registration.
public async Task<(bool Success, string Message)> UserRegistrationAsync(RegisterVm register)
	string message = ResigstrationValidations(register);
	if (!string.IsNullOrEmpty(message))
		return (false, message);

	Users newUser = new();
	newUser.Email = register.Email;
	newUser.FirstName = register.FirstName;
	newUser.LastName = register.LastName;
	newUser.PasswordHash = PasswordHash(register.Password);

	await _myCookieAuthContext.SaveChangesAsync();

	var role = await _myCookieAuthContext.Roles.Where(_ => _.Name.ToUpper() == "USER")

	if (role != null)
		UserRoles userRoles = new();
		userRoles.RoleId = role.Id;
		userRoles.UserId = newUser.Id;

		await _myCookieAuthContext.SaveChangesAsync();

	return (true, string.Empty);
  • (Line: 3-7) Checking user registration model. If the model is invalid then terminates execution by returning the error message.
  • (Line: 13) Fetching password hash value.
  • (Line: 15-16) Saving the user details into the database.
  • (Line: 18-19) Fetching the 'User' role which we are going to assign to the user as default on registering.
  • (Line: 21-29) Saving the user-specific roles into the 'UserRoles' database.
Let's define our method definition into the 'IAccountLogic'.
Task<(bool Success, string Message)> UserRegistrationAsync(RegisterVm register);

Create Registration Razor Pages:

Let's create our user registration razor pages like 'Register.cshtml', 'Register.cshtml.cs' files.
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 RegisterModel : PageModel
    private readonly IHttpContextAccessor _httpContextAccessor;
    private readonly IAccountLogic _accountLogic;
    public RegisterModel(IHttpContextAccessor httpContextAccessor,
    IAccountLogic accountLogic)
        _httpContextAccessor = httpContextAccessor;
        _accountLogic = accountLogic;

    public RegisterVm RegisterForm { get; set; }

    public string ErrorMessage { get; set; }

    public bool IsUserRegistrationSuccessfull { get; set; }

    public async Task<IActionResult> OnGetAsync()
        if (_httpContextAccessor.HttpContext.User.Identity.IsAuthenticated)
            return Redirect("/");
        return Page();

     public async Task<IActionResult> OnPostAsync()
        var registration = await _accountLogic.UserRegistrationAsync(RegisterForm);
        if (!registration.Success)
            ErrorMessage = registration.Message;
            IsUserRegistrationSuccessfull = true;
        return Page();
  • (Line: 11-12) Injected 'IHttpContextAccessor', 'IAccountLogic' into the constructor.
  • (Line: 18-19) The 'RegisterVm' property is used for the form model binding. Model binding is enabled by decorating the property with the 'BindProperty'.
  • (Line: 21) The 'ErrorMessage' property displays the form validation error message.
  • (Line: 23) The 'IsUserRegistrationSucceful' property is used to display the registration success message.
  • (Line: 25-36) The 'OnGetAsync' method gets invoked for the HTTP GET requests. This means it will load the registration form.
  • (Line: 27-30) Here we are restricting the authenticated user to not accessing the registration form.
  • (Line: 34-46) The 'OnPostAsync' method gets invoked by the post request(eg: registration form submission).
  • (Line: 36) Invoking the user registration method like 'UserRegistrationAsync()'.
@page "/identity/account/register"
@model RegisterModel

<div class="container">
    <div class="row text-center">
        <div class="col">
            @if (!string.IsNullOrEmpty(Model.ErrorMessage))
                <div class="alert alert-danger" role="alert">
            else if (Model.IsUserRegistrationSuccessfull)
                <div class="alert alert-success" role="alert">
                    Registered Successfuly, now click here to login
    <div class="row">
        <div class="col-md-6 offset-md-3">
            <form method="POST">
                <legend>User Registration</legend>
                <div class="mb-3">
                    <label for="txtEmail" class="form-label">Email</label>
                    <input asp-for="RegisterForm.Email" type="text" class="form-control" id="txtEmail" />
                <div class="mb-3">
                    <label for="txtFirstName" class="form-label">First Name</label>
                    <input asp-for="RegisterForm.FirstName" type="text" class="form-control" id="txtFirstName" />
                <div class="mb-3">
                    <label for="txtLastName" class="form-label">Last Name</label>
                    <input asp-for="RegisterForm.LastName" type="text" class="form-control" id="txtLastName" />
                <div class="mb-3">
                    <label for="txtPassword" class="form-label">Password</label>
                    <input asp-for="RegisterForm.Password" type="password" class="form-control" id="txtPassword" />
                <div class="mb-3">
                    <label for="txtConfirmPassword" class="form-label">Confirm Password</label>
                    <input asp-for="RegisterForm.ConfirmPassword" type="password" class="form-control"
                        id="txtConfirmPassword" />
                <button type="submit" class="btn btn-primary">Register</button>

(1)Registration Form:
(2)Registration form with an error message
(3)Successful registration message.

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.


Follow Me:


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

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

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

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

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

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti