Tell me more ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
up vote 1 down vote favorite
1

While working on a new project with MVC3, a DI framework (Ninject), and unit tests (NUnit) paired with mocks (Moq), I found setting up the Membership Provider felt a bit "awkward". I've run into tasks that seem disproportionally hard, just as others have: injecting a repository to the provider, creating unit tests, and mocking the provider.

This led me to a SO question on alternatives to the standard Membership provider (in turn linking to another interesting question on whether to roll your own authentication system), which didn't get as much attention as the votes on the question would warrant.

So I'm finally left with the question: Does anyone know what the future for Authentication in ASP.NET is? Or more specifically: did Microsoft provide any (official) insights on their direction for authentication?

I couldn't find any blog posts from MS employees/teams. The only real related thing I could find was this highly upvoted ASP.NET uservoice ticket which doesn't seem to have any official response.

share|improve this question
1  
Whose crystal ball do you want us to use? – Oded♦ Apr 17 '12 at 18:43
2  
Hmm? I'm not looking for crystal ball answers. I'm just curious if there's any (semi)official indications of where Microsoft is taking this. I'm happy to accept the answer that there isn't any, if that's the case. – Jeroen Apr 17 '12 at 18:46
One thing you can count on is Microsoft obsolescing parts of platforms or even whole platforms. But, don't let that delay your project. – jfrankcarr Apr 17 '12 at 19:11
Update on this topic: SimpleMembership (I know the question's been closed -which is understandable-, but since it's not deleted yet I guess this link can help future visitors.) – Jeroen Sep 14 '12 at 9:29

closed as not constructive by Oded♦, Bernard, Walter, Jim G., ChrisF♦ Apr 23 '12 at 19:24

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.

1 Answer

up vote 2 down vote

I don't know anyone at Microsoft to ask.. BUT here's some reasons I will speculate on:

-The membership currently works with windows apps, web apps, mobile apps, and webservices...

-Its basic implementation is very easy (aspnet_regsql) and can be re-implemented (fairly easy to implement your own provider)..

-It was demonstrated in their Mix '11 Odata presentation as a security "feature".. and other than some paradigm shifts in programming styles embraced by the masses, it really works just fine..

so based on that, I'd say it's going to be around for a while. Or at least it's solid enough for them to not worry about changing it for at least a while more...

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.