Windows and Anonymous Authentication in .Net Core 2.0
I’m trying to mix Windows and Anonymous authentication in a .Net Core 2.0 empty web app. I would like to avoid the [Authorize] attribute as I do not want to use Mvc or controllers.
I’m trying to mix Windows and Anonymous authentication in a .Net Core 2.0 empty web app. I would like to avoid the [Authorize] attribute as I do not want to use Mvc or controllers.
This is one of this things that should be extremely simple and I just can’t work out why it’s not working.
I’ve been studying ASP.NET 5 for some time now and there is something I’m yet confused. To implement authentication in Web API 2 what I used to do was basically use the OWIN OAuth Authentication Server Middleware. It was simple to use, I could configure just what I needed and there wasn’t a bunch of stuff I needed to put on the app without need for it.
Ok, I’ve read every thread & question I can find with this error and surprisingly have not found a solution. I’m trying to require Windows authentication on my IIS hosted WCF service (.NET 4.0) which, until now, has been optional. I have had a Windows authentication enabled endpoint available on the server for a while with several remote applications successfully using it. I’m now trying to switch our web applications and other server apps that use the WCF service over to this secured endpoint by giving them the exact same client configuration as the working remote clients, but the server apps are receiving a 401 with the message:
I’m trying something quite exotic I believe and I’m facing a few problems, which I hope can be solved with the help of the users here on StackOverflow.
I am working with a self-hosted OWIN application and am trying to figure out how to require authentication/authorization for all requests (or arbitrary requests).
Now I’m trying to work with System.Web.Routing. All is just fine, but I can’t understand how to make form authentication work with url routing (return url, redirection, etc). Google says nothing. Help! 🙂
Last night I was working on a new project using FormsAuthentication and was customizing the ticket to include a security token so if the user logs off in one browser it logs off in all of them. In looking at the latest iteration of ASP.net Identity, it looks like it already has this functionality built in.
I am using .NET 3.5.
Also, Forms Authentication is used.
I am experiencing problems with Forms Authentication. When I try to load my Login.aspx page neither javascript nor stylesheets do not load.
Here is part of my web.config file