Skip to main content

Authorization In Blazor WebAssembly

In this article, we are going to understand the authorization flow using user roles and claims in the blazor webassembly application.

Create A Sample Blazor WebAssembly Application:

Let's create a sample blazor webassembly application for our demo. We can use any IDE for the application development but the most recommended is Visual Studio 2019(version 16.8.*) and Visual Studio Code.

Authentication Setup:

To implement authorization first user need to be authenticated. So here we will implement some fake user authentication with some roles and claims. For complete authentication, implementation checks my blogs like Access Token and Refresh Token.
Package Manager
Install-Package Microsoft.AspNetCore.Components.Authorization -Version 5.0.1
.Net CLI
dotnet add package Microsoft.AspNetCore.Components.Authorization --Version 5.0.1
A core component of blazor authentication is 'Microsoft.AspNetCore.Components.Authorization.AuthenticationStateProvider', here we going to implement it by customizing it.
Auth/CustomAuthStateProvider.cs:
using System.Security.Claims;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Components.Authorization;

namespace BW.Auth.Auth
{
  public class CustomAuthStateProvider : AuthenticationStateProvider
  {
   public override async Task<AuthenticationState> GetAuthenticationStateAsync()
   {
	var identity = new ClaimsIdentity(new []{
	 new Claim(ClaimTypes.Name,"Naveen"),
	 new Claim(ClaimTypes.Role, "user"),
	 new Claim(ClaimTypes.Role, "admin")
	},"Fake Auth");

	var user = new ClaimsPrincipal(identity);
	return await Task.FromResult(new AuthenticationState(user));
   }
  }
}
  • Here we added roles like 'user' and 'admin' to my authentication.
Now let's import required namespaces into the _Import.razor file.
_Import.razor:
@using BW.Auth.Shared
@using Microsoft.AspNetCore.Components.Authorization
@using Microsoft.AspNetCore.Authorization
Now register the required service in Program.cs file
Program.cs:
builder.Services.AddScoped<AuthenticationStateProvider,CustomAuthStateProvider>();
builder.Services.AddOptions();
builder.Services.AddAuthorizationCore();
Now add the 'CascadingAuthenticationState' and 'AuthorizeRouteView' components in the App.razor file.
App.razor:
<CascadingAuthenticationState>
<Router AppAssembly="@typeof(Program).Assembly">
  <Found Context="routeData">
	<AuthorizeRouteView RouteData="@routeData" DefaultLayout="@typeof(MainLayout)" />
  </Found>
  <NotFound>
	<LayoutView Layout="@typeof(MainLayout)">
		<p>Sorry, there's nothing at this address.</p>
	</LayoutView>
  </NotFound>
</Router>
</CascadingAuthenticationState>

Roles Authorization On AuthorizeView Component:

The AuthorizeView component supports roles based authorization base on the role we can render the content inside of it.
Index.razor:
@page "/"

<AuthorizeView Roles="superadmin">
    <Authorized >
        <div>Hi @(context.User.Identity.Name), hurray you have 'super admin' role, you can claim this offer</div>
    </Authorized>
</AuthorizeView>
<AuthorizeView Roles="admin">
    <Authorized >
        <div>Hi @(context.User.Identity.Name), hurray you have 'admin' role, you can claim this offer</div>
    </Authorized>
</AuthorizeView>
<AuthorizeView Roles="user">
     <Authorized>
        <div>Hi @(context.User.Identity.Name), hurray you have 'user' role ,Claim your user offers  </div>
    </Authorized>
</AuthorizeView>
Here we rendered 3 AuthorizeView components with respective roles to them. For my fake authentication, I have only roles like 'admin' and 'user'. So if run the application for me content inside of the 'superadmin' will not render.

We can also configure multiple roles on the AuthorizeView component with comma separation. So in this process, if we have at least one role then AuthorizeView renders.
Index.razor:
@page "/"

<AuthorizeView Roles="superadmin, admin">
    <Authorized >
        <div>Hi @(context.User.Identity.Name), this offer can claim by users with role either 'superadmin' or'admin'
        </div>
    </Authorized>
</AuthorizeView>
  • Here we configure multiple roles with comma separation, so to render this AuthorizeView component user should have at least one role.

Policy-Based Roles Authorization On AuthorizeView Component:

The policy is a set of rules. In the case of roles the policy will group the set of roles, so the user at least one role in the policy group then the user satisfied that policy, and then the AuthorizeView component renders.
Program.cs:
builder.Services.AddAuthorizationCore(options => {
	options.AddPolicy("mypolicy", policy => {
		policy.RequireRole("admin","superadmin");
	});
});
  • Here we grouped our roles under a policy named 'mypolicy'. Now we can use this policy name to authorize the user.
Pages/Index.razor: 
@page "/"

<AuthorizeView Policy="mypolicy">
    <Authorized >
        <div>Hi @(context.User.Identity.Name), this offer can claim by users with role either 'superadmin' or'admin'
        </div>
    </Authorized>
</AuthorizeView>
  • Here AuthorizeView component renders the users who matched with at least one role that is grouped under the policy.

Roles Authorize Attribute To Page Components:

The Authorize attribute will be used on Page components. One thing to remember this will not work for normal components.  Based on the user role using the authorize attribute we can deny or allow the page access to the user.
Index.razor:
@page "/"
@attribute [Authorize(Roles="admin")]
  • Here our Index page component only accessed by the users who have an 'admin' role.
We can pass multiple roles with command separation, in this case, the user that matches at least one role can access the page.
Index.razor:
@page "/"
@attribute [Authorize(Roles="admin,superadmin")]
We can set multiple Authorize attributes on our Page Component, in this case, the user should have match the roles specified in each attribute.
Index.razor:
@page "/"
@attribute [Authorize(Roles="admin")]
@attribute [Authorize(Roles="user")]
  • User's having both roles only can access the Index page component.
we can also use the roles policy with this authorized attribute.
Index.razor: 
@page "/"
@attribute [Authorize(Policy="admin")]
  • Here users that match at least one role under the policy group will access this page.

Claims-Based Authorization:

The Claims mean key-value pair of data which something like user information. To use claims-based authorization we need to write the policy for it, which means we can't use claims directly like we do in the case of roles.

Let's update some claims to my login.
Auth/CustomAuthStateProvider.cs:
var identity = new ClaimsIdentity(new []{
	new Claim(ClaimTypes.Name,"Naveen"),
	new Claim("PageAccesskey", "1"),
	new Claim("PageAccesskey", "2")
},"Fake Auth");
  • Here I have claims like 'PageAccessKey' with 2 different values like '1' and '2'.
In claims-based authorization, we need to write a policy for authorization. So policy can be written in such a way to check whether a user is having a specific claim or not that is independent of value to that claim.
Program.cs:
builder.Services.AddAuthorizationCore(options => {
	options.AddPolicy("myAccessPolicy", policy => {
		policy.RequireClaim("PageAccesskey");
	});
});
  • Here we check a claims policy where users must have the claim to satisfy this policy. One more thing if we observe here we are not checking the value of the cliams.
Now we can use this claims policy on AuthorizeViewComponent
Pages/Index.razor:
<AuthorizeView Policy="myAccessPolicy" >
    <Authorized >
        <div>Hi @(context.User.Identity.Name)
        </div>
    </Authorized>
</AuthorizeView>
  • So here claims policy check whether the user has the registered claim or not.
Another way of writing claims policy is by defining the values of the claim and then the user should at least have one claim value registered under the policy.
Program.cs:
options.AddPolicy("myAccessPolicy", policy => {
	policy.RequireClaim("PageAccesskey","1","2","3");
});
  • Here now claims policy registered values of the claims as well. So in this case users should have this claim and also should match with at least one of the values of the claim.
We can also use the Authorize attribute with the claim policy to protect the page component like we did use the roles policy.

So that's all about the authorization in the blazor webassembly application.

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

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

Refer:

Follow Me:

Labels:

Comments

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

.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

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
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

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
8 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
5 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

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

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot
Post a Comment
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