Skip to main content

Blazor Server Authentication And Authorization Using Microsoft AspNetCore Identity[.NET6]

In this article, we are going to do a small demo on Blazor Server authentication and authorization using Microsoft AspNetCore Identity.

Microsoft AspNetCore Identity Library:

AspNetCore Identity:
  • Built-in login functionality library that supports authentication of all different .NET applications.
  • Provides rich authentication UI pages and customizable as well.
  • Adoptable for External Authentication providers like 'Google', 'Facebook', 'Outlook'.
  • Can be integrated with other authentication like 'IdentityServer4', 'Azure Active Directory', 'Azure Active Directory B2C(Azure AD B2C)'.

Create A .NET6 Blazor Server App With Individual Authentication:

Let's create a .Net6 Blazor Server sample application with individual authentication 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.
CLI command
dotnet new blazorserver -o Your_Project_Name -au Individual


IdentityDbContext loads from the 'Microsoft.AspNetCore.Identity.EntityFrameworkCore'. By default 'IdentityDbContext' implemented file created into our project like 'Data/ApplicationDbContext.cs'. So the IdentityDbContext can control all our authentication tables like 'Users', 'Roles', 'Claims' etc implicitly.
We can observe 'ApplicationDbContext' registered in 'Program.cs'.
Here default database is configured to 'Sqllite', but for this demo, we are going to use 'Microsoft SQL Database'. So let's install the SQL package which is an extension for the entity framework core.
Package Manager
Install-Package Microsoft.EntityFrameworkCore.SqlServer -Version 6.0.1

.NET CLI Command:
dotnet add package Microsoft.EntityFrameworkCore.SqlServer --version 6.0.1

Now update the 'ApplicationDbContext' registration to use the 'SQL' database and also add the connection string in the appsetting.json file.

Create Identity Tables:

Using entity framework migration we can update the database to create our tables that can be interacted by the 'IdentityDbContext'. So by default, we can observe the migration files at 'Data/Migration'. So to update the database run the below command(for running the migration files against the database).
dotnet ef database update

On running the above command any error occurs that related to migration files, then delete the existing migration files and create a new migration with the below command.
dotnet ef migrations add Your_Migration_Name_Any_Name
So to reflect migration changes in the database need to run the above-mentioned update command.

Identity tables get created are like:
  • The 'AspNetUsers' table for to store user authentication information.
  • The 'AspNetRoles' table for the roles information.
  • The 'AspNetClaims' table for user-related claims.
  • The 'AspNetUserTokens' table for user authentication tokens.
  • The 'AspNetUserLogins' table for user associated logins.
  • The 'AspNetUserRoles' table for users mapped with roles.
  • The 'AspNetRoleClaims' table for roles with specified claims.
Now we can run and check the pages like 'Registration' and 'login'.
Registration Page:-
Login Page:-
After Successful Login:-


In the Blazor server application, a built-in provider called AuthenticationStateProvider provides the authenticated user information into the Blazor Components. This AuthenticationStateProvider reads the data from the 'HttpContext.User', Since blazor components can't read the 'HttpContext' of request they depend on the AuthenticationStateProvider.

So in our project, we have an auto-generated class like 'RevalidatingIdentityAuthenticationStateProvider' that inherits the 'Microsoft.AspNetCore.Components.Server.RevalidatingServerAuthenticationStateProvider' that inherits the 'Microsoft.AspNetCore.Components.Server.ServerAuthetnicationStateProvider' that implements the 'Microsoft.AspNetCore.Components.Authorization.AuthenticationStateProvider'. So from the we can understand that our 'RevlidatingIdentityAuthenticationStateProvider' is a custom implementation for our 'Microsoft.AspNetCore.components.Authorization.AuthenticationStateProvider'.

In 'Program.cs' file we can observe the registration of 'AuthenticationStateProvider'.

Now this 'AuthenticationStateProvider' will be used as Cascading property inside of any Blazor Component that is possible because of the 'CascadingAuthenticationState' Blazor component in the 'App.razor'.

AspNetCore Identity UI:

The 'Microsoft.AspNetCore.Identity.UI' package is a 'Razor Class Library'. This library is bundled with all rebuild-authentication logic and the razor pages(Registration, Login, ForgotPasswor, etc razor pages).

So to load all Identity UI can be done by registering the 'DefaultIdentity' service in Program.cs file.

By default, the 'Areas/Identity' folder contains very few files. So we can override the functionality of Identity by adding them explicitly here(In upcoming steps we can understand how to customize them all).

Authentication Middleware:

In an application, authentication is enabled by registering the authentication middlewares.

Generate Identity Files For Explicit Customization:

We can customize the Identity authentication logic or UI pages by generating the files explicitly inside of the 'Area/Identity' folder. So that means generating explicit files will override the default authentication logic or pages inside of the 'Microsoft.AspNetCore.Identity.UI'(Razor class library).

So follow the steps to generate the identity UI files explicitly:-

Step 1:-
Install the 'Microsoft.VisualStudio.Web.CodeGeneration.Design' NuGet package.
dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design

Step 2:-
Install the dotnet scaffolder globally into your system.
dotnet tool install -g dotnet-aspnet-codegenerator

Step 3:-
Now run the identity scaffolder to generate the UI files
dotnet aspnet-codegenerator identity -dc {Your_Project_Name}.Data.ApplicationDbContext

Now after completing the above steps you observe all identity files generated as below


Let's implement the claims base authorization. So let's add a few claims in the 'AspNetUserClaims' table for a user.

Now create a claims-based authorization policy in the Program.cs
builder.Services.AddAuthorizationCore(options => {
	options.AddPolicy("pageview-policy", policy => {
  • Any component that is decorated with this policy then application only allows the users that contain the specified claim type and its value.
Now on 'Counter.razor' page decorate with the policy-based 'Authorize' attribute. 
@attribute [Authorize(Policy ="pageview-policy")]
Now if we try to access the page without authentication or without proper authorization page will show an error message as below

Support Me!
Buy Me A Coffee PayPal Me

Video Session:

Wrapping up:

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

Follow Me:


  1. This not clear at all here:
    "Now update the 'ApplicationDbContext' registration to use the 'SQL' database and also add the connection string in the appsetting.json file."

    1. Hi

      By default ApplicationDbContext service registration has 'UseSQLite'

      Change it to 'UseSQLServer'
      And also need to add the SQl server connection string value in app settings.json

  2. It looks that in latest version .net core 6.0.1 old Blazor Authorization files does not work well. Also @attribute [Authorize(Roles = "admin,superuser")] is always unauthorized. Did day change that stuff?

    1. May be auth cookie doesn't have Roles as claims

      I think core identity not adding roles as default claims into the auth cookie.
      we need to customize add it


Post a Comment

Popular posts from this blog

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

.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

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

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http