I was following this doc to enable login or registration via an MS account on my website. I did everything instructed on the page and getting this error while trying to use the feature.
I’m currently experiencing an issue with some users of an ASP.NET 4.8 Web API application hosted on Windows Server 2012 and IIS. The following properties are not returning that user’s correct user name, and instead returning the name of a service account used for this server:
I had the following configuration:
After analyzing a lot of examples online and the asp.net core + react authentication given template, I noticed that all of them do NOT use redux store. At first I tough that you should not use them but it could also be just an example application to show roughly how to execute it in a simple manner.
I’m trying to understand the code block below. Everything is fine until the third argument of the tokenHandler.ValidateToken(...) method which is out SecurityToken validatedToken.
I am using Kerberos authentication protocol for my websites.
I just finished my logging/logout code on my asp.net web core application and I am having a problem where the server always returns error 403 forbidden when trying to access a method that needs a specific role. What can be the problem? I checked the database and the role assignment is working fine.
here is an example of a method I wrote for the test:
I am looking for a way to implement authorization to my web app, only certain users should be able to access sensitive parts of the app. I will use windows authentication, the users that are added to the web config will be eligible to access the app, the user management part will only be visible to authorized users.
I am writing a Asp.net MVC 2 application that uses Forms Authentication and currently I am having a problem with our iPhone application in regards to the authentication/login over the web. We have developed a simple iPhone app that uses the the UIWebView control. At this stage, all the app does is navigate to our Asp.Net website. Simple, right? The problem is, that the user cannot get past the login page. The repro steps are:
What is default hash algorithm that ASP.NET membership uses? And how can I change it?