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:

Labels:

Comments

  1. CasperSKApril 12, 2022 at 8:21 PM

    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

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'
3 comments
Read more

.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
6 comments
Read more

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
Post a Comment
Read more

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update 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 the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l
3 comments
Read more

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
7 comments
Read more

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
7 comments
Read more

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the 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 the authentication with HTTP-only JWT cookie then we no need to implement the 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 authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G
2 comments
Read more

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
4 comments
Read more

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
8 comments
Read more

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
2 comments
Read more