Question

是否可以针对两个或更多政策申请授权？我使用的是ASP.NET 5，rc1。

[Authorize(Policy = "Limited,Full")]
public class FooBarController : Controller
{
    // This code doesn't work
}

如果没有，我如何在不使用政策的情况下实现这一目标？有两组用户可以访问此控制器：“完整”和“有限”。用户可以属于“完整”或“有限”，或两者兼而有之。它们只需要属于两个组中的一组即可访问该控制器。

Answer 1

不是你想要的方式;政策旨在累积。例如，如果您使用两个单独的属性，那么它们必须都通过。

您必须在单个策略中评估OR条件。但是您不必在单个处理程序中将其编码为OR。您可以拥有一个具有多个处理程序的需求。如果任一处理程序标记成功，则满足要求。请参阅我的Authorization Workshop中的第6步。

Answer 2

一旦设置了新策略“ LimitedOrFull”（假设它们与声明类型名称匹配），就会创建如下要求：

options.AddPolicy("LimitedOrFull", policy =>
    policy.RequireAssertion(context =>
        context.User.HasClaim(c =>
            (c.Type == "Limited" ||
             c.Type == "Full"))));

https://docs.microsoft.com/en-us/aspnet/core/security/authorization/policies?view=aspnetcore-2.1#using-a-func-to-fulfill-a-policy

Answer 3

Net Core可以选择具有相同AuthorizationRequirement类型的多个AuthorizationHandler。其中只有一个必须成功通过授权 https://docs.microsoft.com/en-us/aspnet/core/security/authorization/policies?view=aspnetcore-2.1#why-would-i-want-multiple-handlers-for-a-requirement

Answer 4

我使用政策和角色：

[Authorize(Policy = "ManagerRights", Roles = "Administrator")]

Answer 5

使用动态创建的按需需求的解决方案最适合我：

创建单独的“有限”和“完整”政策要求的接口：

    public interface ILimitedRequirement : IAuthorizationRequirement { }
    public interface IFullRequirement : IAuthorizationRequirement { }

为授权创建自定义属性：

    [AttributeUsage(AttributeTargets.Class | AttributeTargets.Method, AllowMultiple = true)]
    public class AuthorizeAnyAttribute : AuthorizeAttribute {

        public string[] Policies { get; }

        public AuthorizeAnyAttribute(params string[] policies) : base(String.Join("Or", policies))
            => Policies = policies;
    }

为 ILimitedRequirement 和 IFullRequirement 创建授权处理程序（请注意，这些处理程序处理接口，而不是类）：

    public class LimitedRequirementHandler : AuthorizationHandler<ILimitedRequirement> {

        protected override async Task HandleRequirementAsync(AuthorizationHandlerContext context, ILimitedRequirement requirement) {
            if(limited){
                context.Succeed(requirement);
            }
        }
    }

    public class FullRequirementHandler : AuthorizationHandler<IFullRequirement> {

        protected override async Task HandleRequirementAsync(AuthorizationHandlerContext context, IFullRequirement requirement) {
            if(full){
                context.Succeed(requirement);
            }
        }
    }

如果您的授权处理程序很重（例如，其中一个访问数据库）并且您不希望其中一个进行授权检查，如果另一个已经成功或失败，您可以使用下一个解决方法（记住该顺序处理程序注册直接决定了它们在请求管道中的执行顺序）：

    public static class AuthorizationExtensions {

        public static bool IsAlreadyDetermined<TRequirement>(this AuthorizationHandlerContext context)
            where TRequirement : IAuthorizationRequirement
            => context.HasFailed || context.HasSucceeded
                || !context.PendingRequirements.Any(x => x is TRequirement);

    }


    public class LimitedRequirementHandler : AuthorizationHandler<ILimitedRequirement> {

        protected override async Task HandleRequirementAsync(AuthorizationHandlerContext context, ILimitedRequirement requirement) {
            if(context.IsAlreadyDetermined<ILimitedRequirement>())
                return;

            if(limited){
                context.Succeed(requirement);
            }
        }
    }

    public class FullRequirementHandler : AuthorizationHandler<IFullRequirement> {

        protected override async Task HandleRequirementAsync(AuthorizationHandlerContext context, IFullRequirement requirement) {
            if(context.IsAlreadyDetermined<IFullRequirement>())
                return;

            if(full){
                context.Succeed(requirement);
            }
        }
    }

注册授权处理程序（注意没有“LimiterOrFullRequirementHandler”，这两个处理程序将处理组合策略要求）：

    //Order of handlers is important - it determines their execution order in request pipeline
    services.AddScoped<IAuthorizationHandler, LimitedRequirementHandler>();
    services.AddScoped<IAuthorizationHandler, FullRequirementHandler>();

现在我们需要检索所有 AuthorizeAny 属性并使用 ImpromptuInterface（或任何其他用于动态创建类型实例的工具）为它们动态创建需求：

    using ImpromptuInterface;

    List<AuthorizeAnyAttribute> attributes  = new List<AuthorizeAnyAttribute>();

    foreach(Type type in Assembly.GetExecutingAssembly().GetTypes().Where(type => type.IsAssignableTo(typeof(ControllerBase)))) {
        attributes .AddRange(Attribute.GetCustomAttributes(type , typeof(AuthorizeAnyAttribute))
            .Cast<AuthorizeAnyAttribute>()
            .Where(x => x.Policy != null));
        foreach(var methodInfo in type.GetMethods()) {
            attributes .AddRange(Attribute.GetCustomAttributes(methodInfo , typeof(AuthorizeAnyAttribute))
            .Cast<AuthorizeAnyAttribute>()
            .Where(x => x.Policy != null));
        }
    }
    
    //Add base requirement interface from which all requirements will be created on demand
    Dictionary<string, Type> baseRequirementTypes = new();
    baseRequirementTypes.Add("Limited", typeof(ILimitedRequirement));
    baseRequirementTypes.Add("Full", typeof(IFullRequirement));
    
    Dictionary<string, IAuthorizationRequirement> requirements = new();
    
    foreach(var attribute in attributes) {
        if(!requirements.ContainsKey(attribute.Policy)) {
            Type[] requirementTypes = new Type[attribute.Policies.Length];
            for(int i = 0; i < attribute.Policies.Length; i++) {
                if(!baseRequirementTypes.TryGetValue(attribute.Policies[i], out Type requirementType))
                    throw new ArgumentException($"Requirement for {attribute.Policies[i]} policy doesn't exist");
                requirementTypes[i] = requirementType;
            }
            //Creating instance of combined requirement dynamically
            IAuthorizationRequirement newRequirement = new { }.ActLike(requirementTypes);
            requirements.Add(attribute.Policy, newRequirement);
        }
    }

注册所有创建的需求

    services.AddAuthorization(options => {
        foreach(KeyValuePair<string, IAuthorizationRequirement> item in requirements) {
             options.AddPolicy(item.Key, x => x.AddRequirements(item.Value));
        }
    }

如果默认 AuthorizeAttribute 与自定义 AuthorizeAnyAttribute 的处理方式相同，则上述解决方案允许处理与 OR 组合相同的单一需求

如果上述解决方案是一种矫枉过正的解决方案，则始终可以使用手动组合类型创建和注册：

创建组合的“有限或完整”政策要求：

    public class LimitedOrFullRequirement : ILimitedRequirement, IFullRequirement { }

如果还必须单独使用这两个要求（除了使用组合的“有限或完整”策略），请为单个要求创建接口实现：

    public class LimitedRequirement : ILimitedRequirement { }
    public class FullRequirement : IFullRequirement { }

注册政策（请注意，注释掉的政策是完全可选的注册）：

    services.AddAuthorization(options => {
                options.AddPolicy("Limited Or Full",
                    policy => policy.AddRequirements(new LimitedOrFullRequirement()));
                //If these policies also have single use, they need to be registered as well
                //options.AddPolicy("Limited",
                //  policy => policy.AddRequirements(new LimitedRequirement()));
                //options.AddPolicy("Full",
                //  policy => policy.AddRequirements(new FullRequirement()));
            });

Answer 6

尝试使用角色

[Authorize(Role = "Limited,Full")]

ASP.NET 5针对两个或多个策略进行授权

6 个答案: