在ASP.NET 5,rc1中,是否可能根据两个或多个策略进行授权?
[Authorize(Policy = "Limited,Full")]
public class FooBarController : Controller
{
// This code doesn't work
}
如果不使用策略,我该如何实现这一点?有两组用户可以访问此控制器:“完整”和“有限”。用户可能属于“完整”或“有限”,也可能同时属于两个组。他们只需要属于其中一个组即可访问此控制器。
在ASP.NET 5,rc1中,是否可能根据两个或多个策略进行授权?
[Authorize(Policy = "Limited,Full")]
public class FooBarController : Controller
{
// This code doesn't work
}
不是你想要的方式;策略被设计为累积的。例如,如果您使用两个单独的属性,则它们必须都通过。
您必须在单个策略中评估OR条件。但是您不必将其编码为单个处理程序中的OR。您可以有一个具有多个处理程序的要求。如果任一处理程序标记成功,则已满足该要求。请参见我的授权工作坊中的第6步。
如果设置了一个名为"LimitedOrFull"的新策略(假设它们与声明类型名称匹配),则创建如下要求:
"LimitedOrFull"是指限制或完全控制的意思。
options.AddPolicy("LimitedOrFull", policy =>
policy.RequireAssertion(context =>
context.User.HasClaim(c =>
(c.Type == "Limited" ||
c.Type == "Full"))));
对于我来说,使用按需动态创建的要求解决方案是最好的:
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);
}
}
}
//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
相同,则处理方式相同。 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()));
});
[Authorize(Policy = "ManagerRights", Roles = "Administrator")]
假设你已经在使用
[Authorize(Policy = "Policy_A")]
public class ...
并且
[Authorize(Policy = "Policy_B")]
public class ...
使用
builder.Services.AddAuthorization(options =>
options.AddPolicy("Policy_A", policyBuilder =>
policyBuilder.RequireClaim("UserType", "A")));
builder.Services.AddAuthorization(options =>
options.AddPolicy("Policy_B", policyBuilder =>
policyBuilder.RequireClaim("UserType", "B")));
然后对于您的新PageModel或Controller,请使用
[Authorize(Policy = "Policy_A_or_B")]
public class ...
使用
builder.Services.AddAuthorization(options =>
options.AddPolicy("Policy_A_or_B", policyBuilder =>
policyBuilder.RequireClaim("UserType", "A", "B")));
还可以查看https://learn.microsoft.com/en-us/aspnet/core/security/authorization/policies
[AllowAnonymous]
)。感觉像是反模式,但我可能很蠢! - steamrolla