Skip to main content

ASP.NET MVC 5 and the [AllowAnonymous] attribute

In ASP.NET MVC 4 the [AllowAnonymous] attribute was introduced. This attribute made it a lot easier to secure your whole ASP.NET MVC application. What it allowed you to do is to use a global authentication filter for your application and only allow anonymous access to your login(and register) page. Before you had to add the authorize filter to every controller as there was no way to override the filter when registered globally.

So far the good news… The problem is that in ASP.NET MVC 5, the security model was slightly changed with the introduction of authentication filters. Prior to authentication filters, developers used the Authorization filters to drive some of the authentication tasks for the current request. These tasks can now be separated out to a new custom authentication filter and authorization related tasks can be performed using authorization filters which provide a clean separation of concerns.

The problem is that this new separation doesn’t play nicely with the [AllowAnonymous] attribute. Although you would expect that AllowAnonymous would work at the authentication level, it doesn’t. Instead it is still coupled to the AuthorizationFilter. Why? To not break backwards compatibility.

To fix this and make AllowAnonymous work with the AuthenticationFilter I created my own implementation:

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more