New membership provider interface supporting redirection-based login
OpenID, ADFS, and other redirection-based login protocols don't fit the membership provider interface at all. Please add an interface that can be implemented by an OpenID library decently.
Please try ASP.NET Identity where we added support for OpenID, OAuth provides as first class support in membership. http://blogs.msdn.com/b/webdev/archive/2013/06/27/introducing-asp-net-identity-membership-system-for-asp-net-applications.aspx
Alexander Liberson commented
something like Devise + omniauth for rails.
Aaron Wells commented
The new default should be an OpenID/Federated model, and there should be an MVC controller template that implements OpenAuth. Decoupling the authentication provider just makes more sense today. The membership provider is so 2002.
Shan McArthur commented
Erik, none of these options work with the standard ASP.NET membership provider. They are razor and MVC only, and do not improve the ASP.NET membership model at all. The only thing they do is make it a little easier to build your own membership store. They don't make it easier for implementing off-site authentication or federated authentication. As requested by all the other comments, the membership contract needs a significant rework.
I'm not sure I can mark this one as done or in progress or planned, but we do have some new providers that change everything so we can do these types of things.
In January, we shipped ASP.NET Web Pages and Razor v1. In it was a new feature called SimpleMembership that changed the structure for membership to allow for future types of authentication to be added.
In September, we released the v2 Developer Preview of Web Pages and Razor with added support to SimpleMembership for OAuth (1 and 2) and OpenID.
In our next update we will be adding support for SimpleMembership into MVC 4 and Web Forms vNext.
Check out SimpleMembership and see if it fits your needs.
Thanks everyone. We hear you!
William E. Triest III commented
I'd like to second this thought; in my case we use shibboleth, but it's the same idea as the ones listed above where it does not fit well with the current membership provider.
Graham Charles commented
Eric Jones commented
Luis Abreu commented
+1 on redesigning the membership contract
Eugene Agafonov commented
Actually, membership provider contract should be completely redesigned, as well as providers infrastructure itself.
Peter Kellner commented
Should have sqlserver implementation that supports LINQ2SQL and/or EF without stored procedures. I carry my own ado.net implementation around with me that is getting more and more outdated. +1 on OpenID implementation friendly.