在旧的.net中,我可以像这样从httpcontext请求参数中获取参数
var eventID = filterContext.RequestContext.httpContext.Request.Params["ID"];
我不知道如何在.net核心中实现它
enter code herepublic class HasadminRoleFromAnySiteRequirement : AuthorizationHandler<HasadminRoleFromAnySiteRequirement>,IAuthorizationRequirement{ public HasadminRoleFromAnySiteRequirement() { } protected overrIDe Task HandleRequirementAsync(AuthorizationHandlerContext context,HasadminRoleFromAnySiteRequirement requirement) { //need to call get param from controller to used in the valIDation // something like this //var eventID = filterContext.RequestContext.httpContext.Request.Params["ID"]; // I trIEd the suggestion below but I can't get the parameter from routedata // var mvcContext = context.Resource as Microsoft.AspNetCore.Mvc.Filters.AuthorizationFilterContext; return Task.Fromresult(0); }}解决方法 在处理程序中,您可以执行以下 *** 作
var mvcContext = context.Resource as Microsoft.AspNetCore.Mvc.Filters.AuthorizationFilterContext;if (mvcContext != null){ // examine MVC specific things like routing data.}
如果需要参数值,则在绑定发生之前运行授权属性块.相反,你会转移到控制器内的强制调用.这基本上是resource based authorization,你的参数是一个资源.
您可以将授权服务注入您的控制器;
public class documentController : Controller{ IAuthorizationService _authorizationService; public documentController(IAuthorizationService authorizationService) { _authorizationService = authorizationService; }}
然后稍微改写你的处理程序;
public class documentAuthorizationHandler : AuthorizationHandler<MyRequirement,document>{ public overrIDe Task HandleRequirementAsync(AuthorizationHandlerContext context,MyRequirement requirement,document resource) { // ValIDate the requirement against the resource and IDentity. return Task.CompletedTask; }}
您可以看到此处理程序获取文档,这可以是您喜欢的任何内容,无论是ID的整数,还是某种类型的视图模型.
然后,您可以在HandleRequirementAsync()方法中访问它.
最后,一旦绑定发生,你就可以从你的控制器中调用它;
if (await authorizationService.AuthorizeAsync( User,document,yourRequirement)){}总结
以上是内存溢出为你收集整理的c# – 如何从authrizationhandler .net核心获取params全部内容,希望文章能够帮你解决c# – 如何从authrizationhandler .net核心获取params所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)