WebAPI 5 (Autofac WebApi Integration 5) custom IAutofacActionFilter not assigned to a certain method

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a new ApiController
2. Create a new AuthorizationFilter using IAutofacAuthorizationFilter
3. Create a new BypassFilter using IAutofacActionFilter
4. Within the AuthorizationFilter check if the BypassFilter is set as a custom 
attribute on an action: 
    if (actionContext.ActionDescriptor.GetCustomAttributes<BypassApiKeyFilterAttribute>().Any())
    {
        return;
    }
5. Assign the AuthorizationFilter globally to the controller using
    builder.Register(x => new ApiAuthorizationFilterAttribute())
        .AsWebApiAuthorizationFilterFor<UrlController>()
        .InstancePerApiRequest();
6. Assign the BypassFilter to a certain method:
    builder.Register(x => new BypassApiKeyFilterAttribute())
        .AsWebApiActionFilterFor<UrlController>(x => x.Get(default(string), default(bool)))
        .InstancePerApiRequest();

What is the expected output? What do you see instead?
I except to bypass the apikey authorization, because the AuthorizationFilter 
checks for CustomAttributes, but does not find any. 

What version of Autofac are you using? On what version of .NET/Silverlight?
Autofac 3.1.5
Autofac.WebApi5 (http://www.nuget.org/packages/autofac.webapi5)
.NET 4.5

Please provide any additional information below.
Found this post here: 
http://alexmg.com/post/2012/09/01/New-features-in-the-Autofac-MVC-4-and-Web-API-
(Beta)-Integrations.aspx and tried to do the same in my application.

You can see the code on 
GitHub:https://github.com/ManuelRauber/ShortUrl/tree/Bypass
The relevant files are:

# Bootstrap: 
https://github.com/ManuelRauber/ShortUrl/blob/Bypass/ShortUrl/Common/Bootstrap.c
s#L36
# Api-Attribute: 
https://github.com/ManuelRauber/ShortUrl/blob/Bypass/ShortUrl/Common/ApiAuthoriz
ationFilterAttribute.cs#L50
# Bypass-Attribute: 
https://github.com/ManuelRauber/ShortUrl/blob/Bypass/ShortUrl/Common/BypassApiKe
yFilterAttribute.cs 

Original issue reported on code.google.com by Rauber.M...@gmail.com on 30 Oct 2013 at 7:48

[GoogleCodeExporter]

This issue was closed by revision fd6e9da7b0e9.

Original comment by alex.meyergleaves on 30 Oct 2013 at 2:45

• Changed state: Fixed

[GoogleCodeExporter]

I see what you are trying to achieve with the attributes.

The BypassApiKeyFilterAttribute is not an actual attribute so the reflection 
based GetCustomAttributes implementation will not find it. In the current Web 
API integration even if you did update the filter to derive from 
ActionFilterAttribute, unless you applied it to the action method as an 
attribute Web API would not find it.

I have added a fluent API to the ContainerBuilder for overriding filters at the 
controller or action level. The API works the same way you register filters. 
Under the hood it uses the new IOverrideFilter support.

In your ShortUrl project it would like this:

builder.Register(x => new ApiAuthorizationFilterAttribute())
    .AsWebApiAuthorizationFilterFor<UrlController>()
    .InstancePerApiRequest();

builder.OverrideAuthorizationFilterFor<UrlController>(x => 
x.Get(default(string)));

builder.OverrideAuthorizationFilterFor<UrlController>(x => 
x.Get(default(string), default(bool)));

With this in place there is no need for your BypassApiKeyFilterAttribute. The 
ApiAuthorizationFilterAttribute will simply not be called for the matching 
actions (or controller if you like).

This is currently only available on the MyGet CI feed.

https://www.myget.org/feed/autofac/package/Autofac.WebApi2

I am going to add the same thing to the MVC integration and will then push both 
packages to NuGet.org. If you could grab the package from MyGet and give it a 
test that would be appreciated.

Original comment by alex.meyergleaves on 30 Oct 2013 at 3:03

[GoogleCodeExporter]

This works like a charm!

>>>
The BypassApiKeyFilterAttribute is not an actual attribute so the reflection 
based GetCustomAttributes implementation will not find it. In the current Web 
API integration even if you did update the filter to derive from 
ActionFilterAttribute, unless you applied it to the action method as an 
attribute Web API would not find it.
<<<

Yes, zonk... I read it over and over again. It's mentioned in the 
documentation, but I just didn't got it. Was a bit late yesterday :)

Thank you for the fast patch!

Original comment by Rauber.M...@gmail.com on 30 Oct 2013 at 3:24