AuthorizationHelper and the mere presence of .NET Core 3.0 SDK

All I did was install the .NET 3.0 SDK specifically “dotnet-sdk-3.0.100-win-x86.exe” from here and suddenly I’m not able to login to the app any longer.

• Your Abp package version: v3.8.5
• Your base framework: .Net Core 2.2
• Zero: v7.2.2

INFO  2019-09-24 12:42:10,829 [15   ] soft.AspNetCore.Hosting.Internal.WebHost - Request starting HTTP/1.1 POST http://localhost:63114/Account/Login application/x-www-form-urlencoded; charset=UTF-8 263
INFO  2019-09-24 12:42:10,830 [15   ] ft.AspNetCore.Routing.EndpointMiddleware - Executing endpoint 'SuperCoolProject.Web.Controllers.AccountController.Login (SuperCoolProject.Web.Mvc)'
INFO  2019-09-24 12:42:10,832 [15   ] ore.Mvc.Internal.ControllerActionInvoker - Route matched with {action = "Login", controller = "Account", area = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.JsonResult] Login(SuperCoolProject.Web.Models.Account.LoginViewModel, System.String, System.String, System.String) on controller SuperCoolProject.Web.Controllers.AccountController (SuperCoolProject.Web.Mvc).
INFO  2019-09-24 12:42:10,860 [15   ] ore.Mvc.Internal.ControllerActionInvoker - Executing action method SuperCoolProject.Web.Controllers.AccountController.Login (SuperCoolProject.Web.Mvc) - Validation state: Valid
INFO  2019-09-24 12:42:11,120 [17   ] tion.Cookies.CookieAuthenticationHandler - AuthenticationScheme: Identity.Application signed in.
INFO  2019-09-24 12:42:11,121 [17   ] ore.Mvc.Internal.ControllerActionInvoker - Executed action method SuperCoolProject.Web.Controllers.AccountController.Login (SuperCoolProject.Web.Mvc), returned result Microsoft.AspNetCore.Mvc.JsonResult in 260.8892ms.
INFO  2019-09-24 12:42:11,163 [9    ] matters.Json.Internal.JsonResultExecutor - Executing JsonResult, writing value of type 'Abp.Web.Models.AjaxResponse'.
INFO  2019-09-24 12:42:11,164 [9    ] ore.Mvc.Internal.ControllerActionInvoker - Executed action SuperCoolProject.Web.Controllers.AccountController.Login (SuperCoolProject.Web.Mvc) in 331.6791ms
INFO  2019-09-24 12:42:11,164 [9    ] ft.AspNetCore.Routing.EndpointMiddleware - Executed endpoint 'SuperCoolProject.Web.Controllers.AccountController.Login (SuperCoolProject.Web.Mvc)'
INFO  2019-09-24 12:42:11,164 [9    ] soft.AspNetCore.Hosting.Internal.WebHost - Request finished in 334.7778ms 200 application/json; charset=utf-8
INFO  2019-09-24 12:42:11,176 [9    ] soft.AspNetCore.Hosting.Internal.WebHost - Request starting HTTP/1.1 GET http://localhost:63114/App  
INFO  2019-09-24 12:42:11,177 [9    ] ft.AspNetCore.Routing.EndpointMiddleware - Executing endpoint 'SuperCoolProject.Web.Areas.App.Controllers.HomeController.Index (SuperCoolProject.Web.Mvc)'
INFO  2019-09-24 12:42:11,182 [9    ] ore.Mvc.Internal.ControllerActionInvoker - Route matched with {area = "App", action = "Index", controller = "Home"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.ActionResult] Index() on controller SuperCoolProject.Web.Areas.App.Controllers.HomeController (SuperCoolProject.Web.Mvc).
WARN  2019-09-24 12:42:11,184 [9    ] Mvc.Authorization.AbpAuthorizationFilter - Abp.Authorization.AbpAuthorizationException: Current user did not login to the application!
   at Abp.Authorization.AuthorizationHelper.AuthorizeAsync(IEnumerable`1 authorizeAttributes) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationHelper.cs:line 42
   at Abp.Authorization.AuthorizationHelper.CheckPermissions(MethodInfo methodInfo, Type type) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationHelper.cs:line 107
   at Abp.Authorization.AuthorizationHelper.AuthorizeAsync(MethodInfo methodInfo, Type type) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationHelper.cs:line 56
   at Abp.AspNetCore.Mvc.Authorization.AbpAuthorizationFilter.OnAuthorizationAsync(AuthorizationFilterContext context) in D:\Github\aspnetboilerplate\src\Abp.AspNetCore\AspNetCore\Mvc\Authorization\AbpAuthorizationFilter.cs:line 53

• Steps needed to reproduce the problem.

1. Login using either tenant or host using the default admin/123qwe

Expected: It should login Actual: Nothing appears to happen, there are no JS errors, nothing in the console. The only indication of anything having occurred is the log entry.

[kfrancis]

I’m not sure what happened here. Today, it’s fine. I must have restarted my machine 20 times. I’ll keep an eye on this, sorry.

[maliming]

This happens with a completely brand new project from template: Target Framework: .NET Core (Cross Platform) Template Type: Multi Page Web App Options: “Include login” selected. Latest stable.

Did not reproduce the problem you encountered.