Reading this question, @Pinpoint’s answer and the further discussion on comments, I’m well aware that natively we can’t add an identity provider to our apps developed with ASP.NET 5. One possible replacement for the legacy OAuthAuthorizationServerMiddleware is then provided by the AspNet.Security.OpenIdConnect.Server as I’ve found in many places.
I am trying to get to grips with the new Membership system introduced in ASP.NET MVC 5 and I’ve come across a small issue which I am pretty sure you will be able to help me with.
I’m trying to update a user.
I am attempting to write an ASP.NET application that uses a hybrid authentication scheme.
A user can either have his username and password hash stored in the UserStore, or he can authenticate via Azure Active Directory.
Using Asp.Net Identity 1.0 (RTM version). The default implementation creates an AspNetUsers table. The Id column type is nvarchar(128).
I’m using ASP.NET Identity on my web form application.
Below is my current identity tables:
Why does this example call the SignOut for ExternalCookie before signing in with an ApplicationCookie? Is it just a way to make sure the authentication information is clean? (The full example is here: http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity)
Since there are a lot of changes between each version of Asp.Net Identity, is there a way to get early access to any upcoming changes going forward?
I have an Owin Identity application and another application set up in a virtual directory. The virtual app is set up using traditional forms authentication, and both Web.configs have the same <machineKey> set. I can login using the Identity app, and can see the resulting cookie. However, when I try to access the virtual app it says I am not authenticated.
I need to start a new mvc project and as always I have issues about asp identity, never know where to put it!