Use CasbinAuthorize attribute on ApiController about casbin-aspnetcore HOT 7 CLOSED

@sagilio

from casbin-aspnetcore.

The redirect is because of config issues in my Startup.cs

But it would be good to know whether you believe the Middleware and CasbinAuthorize attribute should work OK when using bearer token authentication.

from casbin-aspnetcore.

Seems to be working with bearer token , but I have to use both standard and casbin attribute:

[Authorize]
[CasbinAuthorize]
public IActionResult MyAction(...)

Is this intended?

from casbin-aspnetcore.

Is this code work? :

[CasbinAuthorize(AuthenticationSchemes = JwtBearerDefaults.AuthenticationScheme)]
public IActionResult MyAction(...)

from casbin-aspnetcore.

Seems to be working with bearer token , but I have to use both standard and casbin attribute:

[Authorize]
[CasbinAuthorize]
public IActionResult MyAction(...)

Is this intended?

No.
Now, casbin middleware does not read the default policy or fallback policy in AuthorizationOptions, So it will not use the AuthenticationSchemes in the default policy.
But, I think we should not read those policies, we will provide AuthenticationSchemes options for this case.

from casbin-aspnetcore.

I tried [CasbinAuthorize(AuthenticationSchemes = JwtBearerDefaults.AuthenticationScheme)]

And it works. I don't need the extra [Authorize] attribute, and I get 401 when token is missing as expected.

Then I removed AuthenticationSchemes = JwtBearerDefaults.AuthenticationScheme And it still works. Now I'm not able reprodue the issue.

from casbin-aspnetcore.

:tada: This issue has been resolved in version 0.2.0 :tada:

The release is available on GitHub release

Your semantic-release bot 📦🚀

from casbin-aspnetcore.