Skip to main content

Custom authorization based on dotnet core policy with Attribute filter

Around 2.5 years back I had written about custom authorization on MVC  Custom authorization on class, action/function, code, area level under Asp.Net MVC application, there are few approaches which are changed in Core version for authorization. Like Authorization filter approach is discouraged since it cannot be unit tested. I believe this is right step but also global or basic authentication could still be driven by Attribute due to enhancing simplicity on codes by focusing on the primary objective rather than writing authorization check everywhere.

The whole approach and usage remain same from the original Post, in this, we would be just looking into making it compatible with dotnet Core MVC. You would need to go through earlier Post to understand the approach that was taken for authorization of a user.

Also, can go through official post: https://docs.microsoft.com/en-us/aspnet/core/security/authorization/policies to understand new approach.

More of all we need to create Requirement i:e PermissionAuthorizationRequirement, Handler for authentication and AppAuthorizeAttribute attribute.

Creating policy requirement

This can accept comparison type and PermissionRule that may be required for authorization.

   /// <summary>  
   /// Permission authorization requirement.  
   /// </summary>  
   /// <seealso cref="IAuthorizationRequirement" />  
   public class PermissionAuthorizationRequirement  
     : Microsoft.AspNetCore.Authorization.IAuthorizationRequirement  
   {  
     /// <summary>  
     /// Gets or sets the comparison mode.  
     /// </summary>  
     /// <value>  
     /// The comparison mode.  
     /// </value>  
     public ComparisonType ComparisonMode { get; set; }  
     /// <summary>  
     /// Initializes a new instance of the <see cref="PermissionAuthorizationRequirement"/> class.  
     /// </summary>  
     public PermissionAuthorizationRequirement()  
     {  
       ComparisonMode = ComparisonType.All;  
     }  
     /// <summary>  
     /// Initializes a new instance of the <see cref="PermissionAuthorizationRequirement" /> class.  
     /// </summary>  
     /// <param name="permissions">The permissions.</param>  
     /// <param name="comparisonType">Type of the comparison.</param>  
     public PermissionAuthorizationRequirement(PermissionRule[] permissions, ComparisonType comparisonType)  
     {  
       Permissions = permissions;  
       ComparisonMode = comparisonType;  
     }  
     /// <summary>  
     /// Gets the permissions.  
     /// </summary>  
     /// <value>  
     /// The permissions.  
     /// </value>  
     public PermissionRule[] Permissions { get; private set; }  
   }

Handler for authorization check of user

This would authorize the user based on saved permissions from DB and required permission to access the requested resource.

 using System.Linq;  
 /// <summary>  
 /// Permission authorization handler.  
 /// </summary>  
 /// <seealso cref="Microsoft.AspNetCore.Authorization.AuthorizationHandler{PermissionsAuthorizationRequirement}" />  
 public class PermissionAuthorizationHandler  
 : Microsoft.AspNetCore.Authorization.AuthorizationHandler<PermissionAuthorizationRequirement>  
 {  
   public PermissionAuthorizationHandler(ISecurityUserRepository securityUserRepository)  
   {  
     // Dependency injection to get value from repository.  
     SecurityUserRepository = securityUserRepository;  
   }  
   /// <summary>  
   /// Gets the security user repository.  
   /// </summary>  
   /// <value>  
   /// The security user repository.  
   /// </value>  
   public ISecurityUserRepository SecurityUserRepository { get; }  
   /// <summary>  
   /// Makes a decision if authorization is allowed based on a specific requirement.  
   /// </summary>  
   /// <param name="context">The authorization context.</param>  
   /// <param name="requirement">The requirement to evaluate.</param>  
   /// <returns>Permission check for user based on Permission requirement.</returns>  
   /// <exception cref="ArgumentException">New comparison type need to be included</exception>  
   protected override async System.Threading.Tasks.Task HandleRequirementAsync(  
     Microsoft.AspNetCore.Authorization.AuthorizationHandlerContext context,  
     PermissionAuthorizationRequirement requirement)  
   {  
     if (!context.User.Identity.IsAuthenticated)  
     {  
       return;  
     }  
     // Getting user id from claims  
     if (!int.TryParse(context.User.FindFirst(System.Security.Claims.ClaimTypes.NameIdentifier)?.Value, out int userId))  
     {  
       return;  
     }  
     // TODO: Implement caching for this  
     var userPermissions = await SecurityUserRepository.GetUserPermissions(userId);  
     var hasPermission = false;  
     switch (requirement.ComparisonMode)  
     {  
       case ComparisonType.All:  
         {  
           hasPermission = requirement.Permissions.All(reqPerm => userPermissions.Any(usrPerm => usrPerm == reqPerm));  
           break;  
         }  
       case ComparisonType.Any:  
         {  
           hasPermission = requirement.Permissions.Any(reqPerm => userPermissions.Any(usrPerm => usrPerm == reqPerm));  
           break;  
         }  
       default:  
         {  
           throw new System.ArgumentException("New comparison type need to be included");  
         }  
     }  
     if (hasPermission)  
     {  
       context.Succeed(requirement);  
     }  
   }  
 }

Attribute filter for invoking implementation

This would allow us to pass permission rule and optional ComparisionType for authorization of a user.

 using Microsoft.AspNetCore.Authorization;  
 using Microsoft.AspNetCore.Mvc;  
 using Microsoft.AspNetCore.Mvc.Filters;  
 using System;  
 using System.Threading.Tasks;  
 /// <summary>  
 /// Application authorization  
 /// </summary>  
 /// <seealso cref="TypeFilterAttribute" />  
 public sealed class AppAuthorizeAttribute  
   : TypeFilterAttribute  
 {  
   /// <summary>  
   /// Initializes a new instance of the <see cref="AppAuthorizeAttribute"/> class.  
   /// </summary>  
   /// <param name="permissions">The permissions.</param>  
   public AppAuthorizeAttribute(params PermissionRule[] permissions)  
     : base(typeof(AppAuthorizeExecuteAttribute))  
   {  
     Arguments = new[] { new PermissionAuthorizationRequirement(permissions, ComparisonType.All) };  
   }  
   /// <summary>  
   /// Initializes a new instance of the <see cref="AppAuthorizeAttribute"/> class.  
   /// </summary>  
   /// <param name="comparisonType">Type of the comparison.</param>  
   /// <param name="permissions">The permissions.</param>  
   public AppAuthorizeAttribute(ComparisonType comparisonType = ComparisonType.All, params PermissionRule[] permissions)  
     : base(typeof(AppAuthorizeExecuteAttribute))  
   {  
     Arguments = new[] { new PermissionAuthorizationRequirement(permissions, comparisonType) };  
   }  
   /// <summary>  
   /// App authorize execution.  
   /// </summary>  
   /// <seealso cref="Attribute" />  
   /// <seealso cref="IAsyncResourceFilter" />  
   private sealed class AppAuthorizeExecuteAttribute  
     : Attribute, IAsyncResourceFilter  
   {  
     /// <summary>  
     /// The authorization service  
     /// </summary>  
     private readonly IAuthorizationService AuthorizationService;  
     /// <summary>  
     /// The required permissions  
     /// </summary>  
     private readonly PermissionAuthorizationRequirement RequiredPermissions;  
     /// <summary>  
     /// Initializes a new instance of the <see cref="AppAuthorizeExecuteAttribute" /> class.  
     /// </summary>  
     /// <param name="requiredPermissions">The required permissions.</param>  
     /// <param name="authorizationService">The authorization service.</param>  
     public AppAuthorizeExecuteAttribute(  
           PermissionAuthorizationRequirement requiredPermissions,  
           IAuthorizationService authorizationService)  
     {  
       RequiredPermissions = requiredPermissions;  
       AuthorizationService = authorizationService;  
     }  
     /// <summary>  
     /// Called asynchronously before the rest of the pipeline.  
     /// </summary>  
     /// <param name="context">The <see cref="T:Microsoft.AspNetCore.Mvc.Filters.ResourceExecutingContext" />.</param>  
     /// <param name="next">The <see cref="T:Microsoft.AspNetCore.Mvc.Filters.ResourceExecutionDelegate" />. Invoked to execute the next resource filter or the remainder  
     /// of the pipeline.</param>  
     /// <returns>  
     /// A <see cref="T:System.Threading.Tasks.Task" /> which will complete when the remainder of the pipeline completes.  
     /// </returns>  
     public async Task OnResourceExecutionAsync(ResourceExecutingContext context, ResourceExecutionDelegate next)  
     {  
       var authResult = await AuthorizationService.AuthorizeAsync(  
               context.HttpContext.User,  
               null,  
               new PermissionAuthorizationRequirement(RequiredPermissions.Permissions, RequiredPermissions.ComparisonMode));  
       if (!authResult.Succeeded)  
       {  
         context.Result = new ChallengeResult();  
         return;  
       }  
       await next?.Invoke();  
     }  
   }  
 }

Registering handler and requirement in MVC

There could be multiple requirements that could be added to it, but for our global one, we need only one.

 service.AddScoped<IAuthorizationHandler, PermissionAuthorizationHandler>();  
 service.AddAuthorization(options =>  
 {  
   options.AddPolicy("PermissionAuthorization", policy =>  
     policy.Requirements.Add(new PermissionAuthorizationRequirement()));  
 });

Usage

Applying authorization to action is much more straightforward.

 [AppAuthorize(ComparisonType.Any, PermissionRule.CanAddBlog, PermissionRule.CanEditBlog)]  
 public ActionResult ViewBlog()  
 {  
 }

Authorization on code level

This is code on custom BaseController to authorize specific area of codes. This is same as the previous post just that new dotnet core custom policy is used.

 /// <summary>  
 /// Executes passed function once authorization is successful.  
 /// </summary>  
 /// <param name="func">The function.</param>  
 /// <param name="comparisonType">Type of the comparison.</param>  
 /// <param name="permissions">The permissions.</param>  
 /// <returns>Result based on passed function if authorization is successful.</returns>  
 public async Task<IActionResult> OnSuccessAuthAsync(  
     Func<IActionResult> func,  
     ComparisonType comparisonType,  
     params PermissionRule[] permissions)  
 {  
   var authResult = await AuthorizationService.AuthorizeAsync(  
     User, null, new PermissionAuthorizationRequirement(permissions, comparisonType));  
   if (authResult.Succeeded)  
   {  
     return func?.Invoke();  
   }  
   return Json(authResult);  
 }  
 /// <summary>  
 /// Executes passed function once authorization is successful.  
 /// </summary>  
 /// <param name="func">The function.</param>  
 /// <param name="permissions">The permissions.</param>  
 /// <returns>Result based on passed function if authorization is successful.</returns>  
 public async Task<IActionResult> OnSuccessAuthAsync(  
   Func<IActionResult> func,  
   params PermissionRule[] permissions)  
 {  
   return await OnSuccessAuthAsync(func, ComparisonType.All, permissions);  
 }




Labels:

Comments

Post a Comment

Popular posts from this blog

Elegantly dealing with TimeZones in MVC Core / WebApi

In any new application handling TimeZone/DateTime is mostly least priority and generally, if someone is concerned then it would be handled by using DateTime.UtcNow on codes while creating current dates and converting incoming Date to UTC to save on servers. Basically, the process is followed by saving DateTime to UTC format in a database and keep converting data to native format based on user region or single region in the application's presentation layer. The above is tedious work and have to be followed religiously. If any developer misses out the manual conversion, then that area of code/view would not work. With newer frameworks, there are flexible ways to deal/intercept incoming or outgoing calls to simplify conversion of TimeZones. These are steps/process to achieve it. 1. Central code for storing user's state about TimeZone. Also, central code for conversion logic based on TimeZones. 2. Dependency injection for the above class to ...
4 comments
Read more

Trim text in MVC Core through Model Binder

Trimming text can be done on client side codes, but I believe it is most suitable on MVC Model Binder since it would be at one place on infrastructure level which would be free from any manual intervention of developer. This would allow every post request to be processed and converted to a trimmed string. Let us start by creating Model binder using Microsoft.AspNetCore.Mvc.ModelBinding; using System; using System.Threading.Tasks; public class TrimmingModelBinder : IModelBinder { private readonly IModelBinder FallbackBinder; public TrimmingModelBinder(IModelBinder fallbackBinder) { FallbackBinder = fallbackBinder ?? throw new ArgumentNullException(nameof(fallbackBinder)); } public Task BindModelAsync(ModelBindingContext bindingContext) { if (bindingContext == null) { throw new ArgumentNullException(nameof(bindingContext)); } var valueProviderResult = bindingContext.ValueProvider.GetValue(bin...
2 comments
Read more

Handling JSON DateTime format on Asp.Net Core

This is a very simple trick to handle JSON date format on AspNet Core by global settings. This can be applicable for the older version as well. In a newer version by default, .Net depends upon Newtonsoft to process any JSON data. Newtonsoft depends upon Newtonsoft.Json.Converters.IsoDateTimeConverter class for processing date which in turns adds timezone for JSON data format. There is a global setting available for same that can be adjusted according to requirement. So, for example, we want to set default formatting to US format, we just need this code. services.AddMvc() .AddJsonOptions(options => { options.SerializerSettings.DateTimeZoneHandling = "MM/dd/yyyy HH:mm:ss"; });
1 comment
Read more

Centralized model validation both for MVC/WebApi and SPA client-side validation using FluentValidation

Validation is one of the crucial parts of any application. It has to validate on both client side and server side requests. What are target features or implementation from this article? Model validation for any given model. Centralized/One code for validation on both server-side and client-side. Automatic validation of model without writing any extra codes on/under actions for validation.  NO EXTRA/ANY codes on client-side to validate any form. Compatible with SPA. Can be compatible with any client-side validation framework/library. Like Angular Reactive form validation or any jquery validation libraries. Tools used in the implementation? FluentValidation : I feel DataAnnotation validation are excellent and simple to use, but in case of complex validation or writing any custom validations are always tricker and need to write a lot of codes to achieve whereas FluentValidations are simple even in case of complex validation. Generally, we need to validate inc...
1 comment
Read more

Architecture solution composting Repository Pattern, Unit Of Work, Dependency Injection, Factory Pattern and others

Project architecture is like garden, we plant the things in certain order and eventually they grow in similar manner. If things are planted well then they will all look(work) great and easier to manage. If they grow as cumbersome it would difficult to maintain and with time more problems would be happening in maintenance. There is no any fixed or known approach to decide project architecture and specially with Agile Methodology. In Agile Methodology, we cannot predict how our end products will look like similarly we cannot say a certain architecture will fit well for entire development lifespan for project. So, the best thing is to modify the architecture as per our application growth. I understand that it sounds good but will be far more problematic with actual development. If it is left as it is then more problems will arise with time. Just think about moving plant vs a full grown tree. Coming to technical side, In this article, I will be explaining about the various techniques ...
Post a Comment
Read more

Blazor 0.5.0 Interop JavaScript from C# and C# to JavaScript call

Blazor provides two-way communication from JS to C# and C# to JS which is called Interop. The version upgrade to Blazor 0.5.0 changed the approach in interactions between cshtml and JS files. The newer version simplifies JS calling by avoiding pre-registration of JS function. In this article, we would see how to call a JS method by passing multiple parameters from cshtml and parameterized call from JS to cshtml. The scenario that is used in this article has a Kendo AutoComplete to search book and populate information based on the selection. An example of a call to JS from cshtml await JSRuntime.Current.InvokeAsync<string>( "searchBook.Init", "#SearchTitle", new DotNetObjectRef(this)); Takeaways from the above example: - JSRuntime.Current give environment to execute out-process JS. - InvokeAsync is a function that would allow executing the JS function. - The searchBook.Init is a JS function call, we would see it in details in the second sec...
Post a Comment
Read more

LDAP with ASP.Net Identity Core in MVC with project.json

Lightweight Directory Access Protocol (LDAP), the name itself explain it. An application protocol used over an IP network to access the distributed directory information service. The first and foremost thing is to add references for consuming LDAP. This has to be done by adding reference from Global Assembly Cache (GAC) into project.json "frameworks": { "net461": { "frameworkAssemblies": { "System.DirectoryServices": "4.0.0.0", "System.DirectoryServices.AccountManagement": "4.0.0.0" } } }, These  System.DirectoryServices  and  System.DirectoryServices.AccountManagement  references are used to consume LDAP functionality. It is always better to have an abstraction for irrelevant items in consuming part. For an example, the application does not need to know about PrincipalContext or any other dependent items from those two references to make it extensible. So, we can begin wi...
Post a Comment
Read more

Channel, ChannelReader and ChannelWriter to manage data streams in multi-threading environment

I came across Channel class while working with SignalR which looks really interesting. By looking into NuGet packages ( https://www.nuget.org/packages/System.Threading.Channels ), it seems just 4 months old. The Channel class provides infrastructure to have multiple reads and write simuletensely through it's Reader and Writer properties. This is where it is handy in case of SignalR where data streaming needs to be done but is not just limited to that but wherever something needs to be read/write/combination of both in a multi-threading environment. In my case with SignalR, I had to stream stock data at a regular interval of time. public ChannelReader<StockData> StreamStock() { var channel = Channel.CreateUnbounded<StockData>(); _stockManager.OnStockData = stockData => { channel.Writer.TryWrite(stockData); }; return channel.Reader; } The SignalR keeps return type of ChannelReader<StockData> open so that whatev...
Post a Comment
Read more

A wrapper implementation for Kendo Grid usage

A wrapper implementation for any heavily used item is always a good practice. Whatever is not written by us and used at a lot of places should be wrapped within specific functionality to keep it future proof and easily changeable. This also encourages DRY principle to keep our common setting at a central place. Kendo UI items are enormous in configuration, one of an issue I find people keep repeating codes for Kendo Grid configuration. They have built very flexible system to have any configuration, but in most of the cases, we do not need all of those complicated configuration. We would try to see a simpler configuration of same. The actual core implementation is bit complex, but we do not have to bother about it once done since the focus is just on usage only. I recommend doing this practice for as simple as jQuery events, form handling or as simple as any notification system. This just won't make things simple but makes codes much more manageable, easy understand, read or open f...
Post a Comment
Read more

Global exception handling and custom logging in AspNet Core with MongoDB

In this, we would be looking into logging and global exception handling in the AspNet Core application with proper registration of logger and global exception handling. Custom logging The first step is to create a data model that we want to save into DB. Error log Data model These are few properties to do logging which could be extended or reduced based on need. public class ErrorLog { /// <summary> /// Gets or sets the Error log identifier. /// </summary> /// <value> /// The Error log identifier. /// </value> [BsonRepresentation(BsonType.ObjectId)] public ObjectId Id { get; set; /// <summary> /// Gets or sets the date. /// </summary> /// <value> /// The date. /// </value> public DateTime Date { get; set; } /// <summary> /// Gets or sets the thread. /// </summary> ...
1 comment
Read more