为什么ASP.NET Core MVC 3.1添加全局授权过滤器后授权处理器会被调用两次且授权失败?
ASP.NET Core 3.1 MVC 授权处理器重复触发问题
项目实现背景
当前项目基于ASP.NET Core MVC 3.1采用基于策略的授权方案,已实现两类授权规则:
- 自定义
ReadAuthorizationRequirement读取操作授权需求,配套实现专属授权处理器完成读取权限校验 - 自定义全局
IpAllowedAuthorizationRequirement请求IP校验规则,请求IP匹配允许范围时即可通过该校验环节
异常现象
在MVC管道中注册全局授权过滤器后,ReadAuthorizationRequirement对应的授权处理器被重复触发两次:
- 首次调用时,授权上下文携带的资源类型为
Microsoft.AspNetCore.Routing.RouteEndpoint,本次校验流程可正常通过 - 第二次调用时,授权上下文携带的资源类型为
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.AuthorizationFilterContextSealed,本次校验流程执行失败,最终导致整个授权流程无法正常完成
现有代码配置
Startup 服务注册与过滤器配置
services.AddAuthorization(options => { options.FallbackPolicy = new AuthorizationPolicyBuilder() .RequireAuthenticatedUser() .Build(); }); services.AddControllersWithViews(options => { options.Filters.Add(new AuthorizeFilter(policy: Constants.Authorization.IpAllowed)); options.Filters.Add(typeof(Filters.RequestLoggingAttribute)); });
ReadAuthorizationHandler 实现
public class ReadAuthorizationHandler : AuthorizationHandler<ReadAuthorizationRequirement> { private readonly IApplicationRouteService _applicationRouteService; public ReadAuthorizationHandler(IApplicationRouteService applicationRouteService) { _applicationRouteService = applicationRouteService; } protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, ReadAuthorizationRequirement requirement) { var roles = AuthorizationHanderHelper.FindRole(_applicationRouteService, context, requirement); if (roles.Any(role => role.Read == true)) { context.Succeed(requirement); } return Task.CompletedTask; } }
IpAllowedAuthorizationHandler 核心校验逻辑
protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, IpAllowedAuthorizationRequirement requirement) { if (context.Resource is Microsoft.AspNetCore.Mvc.Filters.AuthorizationFilterContext mvcContext) { var userIps = ((ClaimsIdentity)context.User.Identity).Claims .Where(c => c.Type == Constants.Authorization.ClaimTypes.IpAddress) .Select(c => c.Value).ToList(); var currentIp = mvcContext.HttpContext.Connection.RemoteIpAddress; var bytes = currentIp.GetAddressBytes(); var badIp = true; foreach (var address in userIps) { if (IPAddress.TryParse(address, out IPAddress testIp)) { if (testIp.GetAddressBytes().SequenceEqual(bytes)) { badIp = false; break; } } } if (!badIp) { context.Succeed(requirement); } else { var routeData = mvcContext.RouteData; var action = routeData.Values["action"] as string; var controller = routeData.Values["controller"] as string; var area = routeData.DataTokens["area"] as string; if (string.IsNullOrEmpty(area) && controller == "Account" && action == "AccessDenied") { mvcContext.ModelState.TryAddModelError("", $"IP izni verilmemiştir! (IP: {currentIp})"); context.Succeed(requirement); } else { context.Fail(); } } } return Task.CompletedTask; }
调试观测结果
通过断点跟踪可定位两次调用的具体状态:
- 第一次调用Read授权处理器时,关联上下文为Endpoint类型,校验顺利通过
- 第二次调用Read授权处理器时,关联上下文为MVC管道内的AuthorizationFilterContext类型,校验未通过,此时IpAllowed授权需求仍处于待处理状态
内容的提问来源于stack exchange,提问作者mesut
相关产品推荐
相关产品推荐

