ASP.NET身份VS简单成员的优点和缺点？ [英] ASP.NET Identity vs Simple membership Pros and Cons?

问题描述

在MVC4我们不得不简单会员。我的看法是简单的会员是一个很好的身份模型试验和有很好的文档进行测试，并没有需要修复，但只是需要升级的电子邮件验证/密码方面重置和所有其他的东西，我们通常要处理构建应用程序时。然而，新的ASP.NET身份模式似乎达到了Vista中实现了超过XP各种各样的东西。我的意思是 AspnetUserClaims 和 AspnetLogins 为 UserAlias​​es 。而微软应该提供给我潺潺的电子邮件部分的一些方法。刚刚讨论了基于这可能是骗人的，我的问题首先查找我的看法是

In MVC4 we had Simple Membership. My opinion is that Simple Membership was a good Identity Model tried and tested with good documentation and didn't need to be fixed but simply needed an upgrade in terms of Email Verification/ Password Reset and all other stuff that we normally have to deal with when building an app. However the new ASP.NET Identity model seems achieve Something of sorts that Vista achieved over XP. I mean AspnetUserClaims and AspnetLogins could have been bunched together as UserAliases. And Microsoft should have provided some methods for the Email part of my babble. Having just discussed my opinion based on first looks which might be deceiving my question is

我试图决定我是否应该从简单会员移动以新的 ASP.NET身份但由于ASP.NET身份模型文档和测试稀疏，相互矛盾的，很难找到使用谷歌。因此，有人可以既体验，请总结利弊？

I am trying to decide whether I should move from Simple Membership to the new ASP.NET Identity but since documentation and tests of ASP.NET Identity model is sparse, conflicting and hard to locate using Google. So can someone with experience of both please summarize the pros and cons?

推荐答案

@Roman引用一些好文章，看起来在ASP.NET身份和成员资格提供模式的利弊。

@Roman references some good articles that looks at the pros and cons of ASP.NET Identity and the membership provider model.

ASP.NET身份会从会员提供的模式，我相信这是一件好事了。有一些明确的问题的简单会员当你想要更高级的安全功能，如果它是什么，不是简单的越多，你结束了创建您自己的安全解决方案。我与前进的 ASP.NET身份，因为它远远超过更具可扩展性的简单会员并虽然文档和支持，现在是弱，我相信它会变得更好，因为它的成熟，就像简单会员一样。如果你能得到过去的成长的烦恼，我相信 ASP.NET身份将会比简单会员一个更好的解决方案是我喜欢的紧密集成 OWIN ，这将是重要的向前发展。至于电子邮件验证是 ASP.NET身份的这里是介绍如何实现这个的文章。你可以 href=\"http://simplesecurity.$c$cplex.com/\">完整的源$ C ​​$ C。而这里介绍的解决方案还提供了与ASP.NET身份

ASP.NET Identity gets away from the membership provider model, which I believe is a good thing. There are some definite problems with Simple Membership when you wanted more advanced security features and if it was anything more than "simple" you ended up creating your own security solution. I am moving forward with ASP.NET Identity because it much more extensible than Simple Membership and although the documentation and support is weak right now I believe it will get better as it matures, just like Simple Membership did. If you can get past the growing pains I believe ASP.NET Identity will be a far better solution than Simple Membership was and I like the tight integration with OWIN, which will be important going forward. As for email verification with ASP.NET Identity, here is an article that describes how to implement this. You can get complete source code here. And the solution described here also provides password reset with ASP.NET Identity.

这篇关于ASP.NET身份VS简单成员的优点和缺点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！