Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

IAuthorizationFilter blocking Smidge route

See original GitHub issue

When I try to use a IAuthorizationFilter implementation, I had to skip when context.RouteData?.Values["bundle"] != null .

There is a solution for this? Maybe I did some misconfiguration?

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

Shazwazzacommented, Aug 23, 2021

I Just published a new 4.0 beta release with the [AllowAnonymous] change if you want to check it out

https://www.nuget.org/packages/Smidge/4.0.0-beta.357 https://www.nuget.org/packages/Smidge.Nuglify/4.0.0-beta.357

1reaction

Shazwazzacommented, Aug 23, 2021

So you are adding a global auth filter to all controllers which will include Smidge controllers and therefore the Smidge controllers will not execute.

A fix could be that we include the [AllowAnonymous] attribute on the smidge controller. I think this controller should always be publicly available since it’s just used for returning css/js.

You should be able to determine the current controller executing in your route values too and could just check for “Smidge” as the controller name and exclude your authz.

Let me know what you think.