Custom Policy-Based Authorization¶ 基于自定义策略的授权
Underneath the covers the role authorization and claims authorization make use of a requirement, a handler for the requirement and a pre-configured policy. These building blocks allow you to express authorization evaluations in code, allowing for a richer, reusable, and easily testable authorization structure.
下面的内容覆盖了role authorization（角色授权） 和claims authorization（声明授权），确保了要求、要求的句柄以及一个预配制策略的使用，这些搭建好的模块允许你在代码中表达授权检测，允许多重的、可重用的以及易于测试的授权结构。
An authorization policy is made up of one or more requirements and registered at application startup as part of the Authorization service configuration, in ConfigureServices in the Startup.cs file.
一个授权策略由一个或者多个要求组成，并且作为授权服务配置的一部分在应用启动阶段进行注册（在Startup.cs文件的ConfigureServices 中）。
public void ConfigureServices(IServiceCollection services) { services.AddMvc(); services.AddAuthorization(options => { options.AddPolicy("Over21", policy => policy.Requirements.Add(new MinimumAgeRequirement(21))); } });
Here you can see an “Over21” policy is created with a single requirement, that of a minimum age, which is passed as a parameter to the requirement.
此处，你可看到新建的“Over21”策略使用了单项需求，表明了最小的年龄要求，并作为一个参数传递给需求。
Policies are applied using the Authorize attribute by specifying the policy name, for example;
通过指定策略名称，使用Authorize 属性应用了该策略：
[Authorize(Policy="Over21")] public class AlcoholPurchaseRequirementsController : Controller { public ActionResult Login() { } public ActionResult Logout() { } }
Requirements¶ 要求
An authorization requirement is a collection of data parameters that a policy can use to evaluate the current user principal. In our Minimum Age policy the requirement we have a single parameter, the minimum age. A requirement must implement IAuthorizationRequirement. This is an empty, marker interface. A parameterized minimum age requirement might be implemented as follows;
授权要求是一个数据参数组成的集合，这些参数可由策略使用来检测当前用户是否是授权用户。在最小年龄策略要求中，有一个单个参数，表示最小年龄。一个要求必须继承IAuthorizationRequirement。这是一个空的、起到标记作用的接口。参数化的最小年龄要求可以像下面这样进行继承。
public class MinimumAgeRequirement : IAuthorizationRequirement { public MinimumAgeRequirement(int age) { MinimumAge = age; } protected int MinimumAge { get; set; } }
A requirement doesn’t need to have data or properties.
一个要求不需要有数据或属性。
What should a handler return?¶ 一个处理器会返回什么
You can see in our handler example that the Handle() method has no return value, so how do we indicate success or failure?
可以看到在处理器的例子中，Handle()方法没有返回值，所以我们如何表明成功或者失败呢？
- A handler indicates success by calling
context.Succeed(IAuthorizationRequirement requirement), passing the requirement that has been successfully validated. - 一个处理器通过调用context.Succeed(IAuthorizationRequirement requirement)来表示成功，向要求传递已经进行了成功验证的信息。
- A handler does not need to handle failures generally, as other handlers for the same requirement may succeed.
- 一般地，一个处理器不需要处理失败信息，因为一个要求的其他处理就会满足条件了。
- To guarantee failure even if other handlers for a requirement succeed, call
context.Fail. - 如果处理器的其他要求验证成功了，仍要传递验证失败信息，可调用context.Fail
Regardless of what you call inside your handler all handlers for a requirement will be called when a policy requires the requirement. This allows requirements to have side effects, such as logging, which will always take place even if context.Fail() has been called in another handler.
无论您在您的处理程序中调用什么，当一个策略需要要求时，一个要求的所有处理程序都将会被调用。这使得要求有副作用，例如日志，尽管context.Fail()已在另一个处理程序被调用，它将总会发生。
Why would I want multiple handlers for a requirement?¶
为什么我需要一个复合处理器？
In cases where you want evaluation to be on an OR basis you implement multiple handlers for a single requirement. For example, Microsoft has doors which only open with key cards. If you leave your key card at home the receptionist prints a temporary sticker and opens the door for you. In this scenario you’d have a single requirement, EnterBuilding, but multiple handlers, each one examining a single requirement.
当需要检测“OR”的关系时，你会为单个的要求执行复合处理器。例如，微软公司有多个门禁，这些门禁只能通过门禁卡打开。如果你把门禁卡忘到家里了，门岗打印一个临时卡片并且为你开门。在这种情境下，你就有了一个单独的要求------EnterBuilding，但是每个符合处理器都检测一个单独的需求。
public class EnterBuildingRequirement : IAuthorizationRequirement { } public class BadgeEntryHandler : AuthorizationHandler<EnterBuildingRequirement> { protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, EnterBuildingRequirement requirement) { if (context.User.HasClaim(c => c.Type == ClaimTypes.BadgeId && c.Issuer == "http://microsoftsecurity")) { context.Succeed(requirement); } return Task.CompletedTask; } } public class HasTemporaryStickerHandler : AuthorizationHandler<EnterBuildingRequirement> { protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, EnterBuildingRequirement requirement) { if (context.User.HasClaim(c => c.Type == ClaimTypes.TemporaryBadgeId && c.Issuer == "https://microsoftsecurity")) { // We'd also check the expiration date on the sticker. context.Succeed(requirement); } return Task.CompletedTask; } }
Now, assuming both handlers are registered when a policy evaluates the EnterBuildingRequirement if either handler succeeds the policy evaluation will succeed.
现在，假定两个处理器都被注册了，当这个策略检查EnterBuildingRequirement 时，如果每个处理器都会成功验证。
Using a func to fufill a policy¶ 使用函数满足策略
There may be occasions where fufilling a policy is simple to express in code. It is possible to simply supply a Func<AuthorizationHandlerContext, bool> when configuring your policy with the RequireAssertion policy builder.
有这种场合，用代码表达一个策略是简单的。这个功能可以这样来实现，当用RequireAssertion 策略构造器配置策略时，简单地提供一个Func<AuthorizationHandlerContext, bool> 。
For example the previous BadgeEntryHandler could be rewritten as follows;
举一个例子，前面的BadgeEntryHandler可以重写如下：
services.AddAuthorization(options => { options.AddPolicy("BadgeEntry", policy => policy.RequireAssertion(context => context.User.HasClaim(c => (c.Type == ClaimTypes.BadgeId || c.Type == ClaimTypes.TemporaryBadgeId) && c.Issuer == "https://microsoftsecurity")); })); } }
Accessing MVC Request Context In Handlers¶ 在处理器中使用MVC请求上下文
The Handle method you must implement in an authorization handler has two parameters, an AuthorizationContext and the Requirement you are handling. Frameworks such as MVC or Jabbr are free to add any object to the Resource property on the AuthorizationContext to pass through extra information.
在授权处理器中必须引用的Handle方法有两个参数，一个是AuthorizationContext ，另一个是你正在处理的Requirement 。诸如MVC或者Jabbr等框架是开放的，可以向AuthorizationContext的Resource属性添加任何对象，以传递特别的信息。
For example MVC passes an instance of Microsoft.AspNetCore.Mvc.Filters.AuthorizationFilterContext in the resource property which is used to access HttpContext, RouteData and everything else MVC provides.
例如，MVC向resource属性传递了Microsoft.AspNetCore.Mvc.Filters.AuthorizationFilterContext 的一个实例，该实例用于连接HttpContext、RouteData以及MVC提供的其他一切。
The use of the Resource property is framework specific. Using information in the Resource property will limit your authorization policies to particular frameworks. You should cast the Resource property using the as keyword, and then check the cast has succeed to ensure your code doesn’t crash with InvalidCastExceptions when run on other frameworks;
使用Resource 属性是由框架指定的。使用Resource属性中的信息将限制你的授权策略至特殊的框架。你将使用as关键字注入Resource特性，并且检测注入已经成功，来保证代码运行到其他框架时不会遇到InvalidCastExceptions 而崩溃。
var mvcContext = context.Resource as Microsoft.AspNetCore.Mvc.Filters.AuthorizationFilterContext; if (mvcContext != null) { // Examine MVC specific things like routing data. }