在ASP.NET MVC重定向擅自控制器 [英] Redirecting unauthorized controller in ASP.NET MVC

问题描述

我在ASP.NET MVC控制器，我已经限制在管理角色：

I have a controller in ASP.NET MVC that I've restricted to the admin role:

[Authorize(Roles = "Admin")]
public class TestController : Controller
{
   ...

如果谁不是在管理角色的用户导航到该控制器他们正在迎接一个空白屏幕。

If a user who is not in the Admin role navigates to this controller they are greeted with a blank screen.

我想什么做的是重定向他们查看，说：你需要在管理角色能够访问这个资源。

What I would like to do is redirect them to View that says "you need to be in the Admin role to be able to access this resource."

这样做，我已经想到的一个办法是对的isUserInRole（每个操作方法检查），如果没有作用，然后返回此信息视图。但是，我不得不把在每个打破了DRY本金和显然是繁琐的维护行动。

One way of doing this that I've thought of is to have a check in each action method on IsUserInRole() and if not in role then return this informational view. However, I'd have to put that in each Action which breaks the DRY principal and is obviously cumbersome to maintain.

推荐答案

创建基于AuthorizeAttribute定制的授权属性，并覆盖OnAuthorization执行要如何完成它的检查。通常情况下，AuthorizeAttribute会如果授权检查失败设置过滤结果HttpUnauthorizedResult。你可以把它设置它为一个的ViewResult（你的错误观点）来代替。

Create a custom authorization attribute based on AuthorizeAttribute and override OnAuthorization to perform the check how you want it done. Normally, AuthorizeAttribute will set the filter result to HttpUnauthorizedResult if the authorization check fails. You could have it set it to a ViewResult (of your Error view) instead.

修改：我有几个博客帖子说进入更详细：

EDIT: I have a couple of blog posts that go into more detail:

• http://farm-fresh-$c$c.blogspot.com/2011/03/revisiting-custom-authorization-in.html


• http://farm-fresh-$c$c.blogspot.com/2009/11/customizing-authorization-in-aspnet-mvc.html

例如：

    [AttributeUsage( AttributeTargets.Class | AttributeTargets.Method, Inherited = true, AllowMultiple = false )]
    public class MasterEventAuthorizationAttribute : AuthorizeAttribute
    {
        /// <summary>
        /// The name of the master page or view to use when rendering the view on authorization failure.  Default
        /// is null, indicating to use the master page of the specified view.
        /// </summary>
        public virtual string MasterName { get; set; }

        /// <summary>
        /// The name of the view to render on authorization failure.  Default is "Error".
        /// </summary>
        public virtual string ViewName { get; set; }

        public MasterEventAuthorizationAttribute()
            : base()
        {
            this.ViewName = "Error";
        }

        protected void CacheValidateHandler( HttpContext context, object data, ref HttpValidationStatus validationStatus )
        {
            validationStatus = OnCacheAuthorization( new HttpContextWrapper( context ) );
        }

        public override void OnAuthorization( AuthorizationContext filterContext )
        {
            if (filterContext == null)
            {
                throw new ArgumentNullException( "filterContext" );
            }

            if (AuthorizeCore( filterContext.HttpContext ))
            {
                SetCachePolicy( filterContext );
            }
            else if (!filterContext.HttpContext.User.Identity.IsAuthenticated)
            {
                // auth failed, redirect to login page
                filterContext.Result = new HttpUnauthorizedResult();
            }
            else if (filterContext.HttpContext.User.IsInRole( "SuperUser" ))
            {
                // is authenticated and is in the SuperUser role
                SetCachePolicy( filterContext );
            }
            else
            {
                ViewDataDictionary viewData = new ViewDataDictionary();
                viewData.Add( "Message", "You do not have sufficient privileges for this operation." );
                filterContext.Result = new ViewResult { MasterName = this.MasterName, ViewName = this.ViewName, ViewData = viewData };
            }

        }

        protected void SetCachePolicy( AuthorizationContext filterContext )
        {
            // ** IMPORTANT **
            // Since we're performing authorization at the action level, the authorization code runs
            // after the output caching module. In the worst case this could allow an authorized user
            // to cause the page to be cached, then an unauthorized user would later be served the
            // cached page. We work around this by telling proxies not to cache the sensitive page,
            // then we hook our custom authorization code into the caching mechanism so that we have
            // the final say on whether a page should be served from the cache.
            HttpCachePolicyBase cachePolicy = filterContext.HttpContext.Response.Cache;
            cachePolicy.SetProxyMaxAge( new TimeSpan( 0 ) );
            cachePolicy.AddValidationCallback( CacheValidateHandler, null /* data */);
        }


    }

这篇关于在ASP.NET MVC重定向擅自控制器的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！