I am wondering if is there any difference of [Authorize] attribute and AuthorizePage(string) method in ASP.NET Core? Project uses ASP.NET Core 3.1. Is there any advantage or disadvantage using one?
I am trying to use a model I created (RoleAssignmentRecord) in my Index.cshtml file (in the Pages folder). Below is my Index.cshtml code:
I have tried various Google searches but am not getting specific results.
I’ve done this before with MVC5 using User.Identity.GetUserId() but that doesn’t seem to work here.
The User.Identity doesn’t have the GetUserId() method.
I have this line in some code I want to copy into my controller, but the compiler complains that
I am working on a web app that needs to integrate with an existing user database. I would still like to use the [Authorize] attributes, but I don’t want to use the Identity framework. If I did want to use the Identity framework I would add something like this in the startup.cs file:
I’m developing an ASP.Net Core web application where I need to create a kind of “authentication proxy” to another (external) web service.
In Web API 2, you used to be able to create an endpoint to issue a token by setting up an OAuth Authorization Server via middleware like below:
I’ve been keeping my head down working on various projects and apparently Microsoft has been busy making some big changes and it’s confusing the hell out of me. ASP.NET Core first came onto my radar when I installed Visual Studio 2017 last year and went to create a new project and suddenly had choices of .NET Framework, .NET Standard, and .NET Core. So I looked into them a little and saw that the latter two are, in some way, abbreviated versions of the full framework. I read this post by Scott Hanselman ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET Core 1.0 I also found this, which steered me away from ASP.NET Core: Choose between ASP.NET and ASP.NET Core. My takeaway was “Core is new, you’re fine to keep using the full framework.” So I created a new ASP.NET MVC site using .NET Framework 4.6.2 and Microsoft.AspNet.Mvc 5.2.3.
I tried this Middleware but the browser still saving files.