ASP.NET Identity 与简单成员资格的优缺点? [英] ASP.NET Identity vs Simple membership Pros and Cons?

问题描述

在 MVC4 中，我们有简单的成员资格.我的观点是 Simple Membership 是一个很好的身份模型，经过良好的文档尝试和测试，不需要修复，只需要在电子邮件验证/密码重置和所有其他内容方面进行升级我们通常在构建应用程序时必须处理.然而，新的 ASP.NET Identity 模型似乎实现了 Vista 在 XP 上实现的某种程度.我的意思是 AspnetUserClaims 和 AspnetLogins 可以作为 UserAliases 组合在一起.微软应该为我胡言乱语的电子邮件部分提供一些方法.刚刚根据第一眼讨论了我的意见，这可能会欺骗我的问题

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 Identity，但由于 ASP.NET Identity 模型的文档和测试很少，使用谷歌很难定位.那么有经验的人可以总结一下优缺点吗?

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 Identity 和成员资格提供程序模型的优缺点.

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

ASP.NET Identity 脱离了成员资格提供程序模型，我认为这是一件好事.当您想要更高级的安全功能时，简单会员 存在一些明确的问题，如果它不仅仅是简单"，那么您最终会创建自己的安全解决方案.我正在继续使用 ASP.NET Identity，因为它比 Simple Membership 更具可扩展性，虽然目前文档和支持很弱，但我相信它会随着它的成熟而变得更好，就像简单会员一样.如果您能克服成长的烦恼，我相信 ASP.NET Identity 将是比 Simple Membership 更好的解决方案，而且我喜欢与 OWIN<的紧密集成/code>，这将是重要的未来.至于使用 ASP.NET Identity 的电子邮件验证，这是一篇介绍如何实现此功能的文章.您可以此处获得完整的源代码.而此处描述的解决方案也提供了使用 ASP.NET Identity 的密码重置.

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 Identity 与简单成员资格的优缺点?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！