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:

Popular posts from this blog

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.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...