主要目標(biāo)是在 OIDC 用戶具有類型為“BlockedFrom”的自定義聲明（在 ClaimsTransformation 中添加）時(shí)阻止訪問門戶。我已經(jīng)通過Startup.Configure方法中的中間件解決了它。一般原因是保留原始請(qǐng)求 URL 而不重定向到 /Account/AccessDenied 頁面。app.Use((context, next) =>{    var user = context.User;    if (user.IsAuthenticated())    {        // Do not rewrite path when it marked with custom [AllowBlockedAttribute]!        // /Home/Logout, for example. But how?        //        if (user.HasClaim(x => x.Type == UserClaimTypes.BlockedFrom))        {            // Rewrite to run specific method of HomeController for blocked users            // with detailed message.            //            context.Request.Path = GenericPaths.Blocked;        }    }    return next();});但是有一個(gè)意想不到的結(jié)果：Logout方法也HomeController被阻塞了。用戶被阻止時(shí)無法注銷，哈哈！想到的第一件事 - 檢查自定義屬性，例如[AllowBlockedAttribute]. 中間件中的硬編碼路徑常量看起來很瘋狂。如何訪問中間件中調(diào)用方法的屬性？另一種（更優(yōu)雅）的方法是將此邏輯自定義BlockedHandler : AuthorizationHandler<BlockedRequirement>并在Startup.ConfigureServices方法的MVC 選項(xiàng)中將其分配為一般策略：services.AddSingleton<IAuthorizationHandler, BlockedHandler>();services.AddMvc(options =>{    var policy = new AuthorizationPolicyBuilder()        .RequireAuthenticatedUser()        .AddRequirements(new BlockedRequirement())        .Build();    // Set the default authentication policy to require users to be authenticated.    //    options.Filters.Add(new AuthorizeFilter(policy));}).SetCompatibilityVersion(CompatibilityVersion.Version_2_1);假設(shè)實(shí)現(xiàn)BlockedHandler：public class BlockedHandler : AuthorizationHandler<BlockedRequirement>{    protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, BlockedRequirement requirement)    {        if (!context.User.HasClaim(c => c.Type == UserClaimTypes.BlockedFrom))        {            context.Succeed(requirement);            return Task.CompletedTask;        }