如何在＆QUOT; ASP.Net身份＆QUOT;与＆QUOT比较; Windows标识基础＆QUOT;？ [英] How does the "ASP.Net Identity" compare with "Windows Identity Foundation"?

问题描述

我发现这个好文章，显示了ASP.Net身份框架的演变：
<一href=\"http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity\">http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity

I found this nice article that shows the evolution of the ASP.Net identity frameworks: http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity

不过，我感兴趣的是Windows身份验证框架（WIF）如何适应新ASP.Net身份框架中的图片。他们是另一套微软的竞争实现的？

However, I'm interested in how the Windows Identity Framework (WIF) fits into the picture with the new ASP.Net Identity Framework. Are they yet another set of competing Microsoft implementations?

此外，如果开发商有兴趣支持SAML身份验证（其中WIF支持），Active Directory身份验证和表单验证，你会选择哪一个？

Furthermore, if a developer is interested in supporting SAML authentication (which WIF supports), Active Directory authentication, and Forms Authentication, which would you choose?

推荐答案

感谢nzpcmad帮我问正确的问题。

Thanks nzpcmad for helping me ask the right questions.

更多的研究后，如果我理解这一切正确，使用新的ASP.Net身份最大的好处是，它是建立在OWIN模型之上。

After more research, if I understand this all correctly, the biggest advantage of using the new ASP.Net Identity is that it is built on top of the OWIN model.

微软正在开发名为Microsoft.Owin.Security.WsFederation基于OWIN-WS联合组件。它仍处于测试阶段，但我认为它实际上是建立在WIF，因为WIF类都搬进了核心框架.NET 4.5的。更多信息可以在这里找到：<一href=\"http://www.cloudidentity.com/blog/2014/02/20/ws-federation-in-microsoft-owin-componentsa-quick-start/\" rel=\"nofollow\">http://www.cloudidentity.com/blog/2014/02/20/ws-federation-in-microsoft-owin-componentsa-quick-start/这里<一个href=\"http://blogs.msdn.com/b/webdev/archive/2014/02/21/using-claims-in-your-web-app-is-easier-with-the-new-owin-security-components.aspx\" rel=\"nofollow\">http://blogs.msdn.com/b/webdev/archive/2014/02/21/using-claims-in-your-web-app-is-easier-with-the-new-owin-security-components.aspx.

Microsoft is working on an OWIN-based WS-Federation component called Microsoft.Owin.Security.WsFederation. It is still in beta, but I think it is actually built on WIF, since the WIF classes were all moved into the core framework as of .Net 4.5. More information can be found here: http://www.cloudidentity.com/blog/2014/02/20/ws-federation-in-microsoft-owin-componentsa-quick-start/ and here http://blogs.msdn.com/b/webdev/archive/2014/02/21/using-claims-in-your-web-app-is-easier-with-the-new-owin-security-components.aspx.

所以我不认为这个问题是：ASP.Net身份与WIF。我认为问题是：OWIN与非OWIN

So I don't think the question is: ASP.Net Identity versus WIF. I think the question is: OWIN versus non-OWIN.

所以，我认为回答我的问题：越是面向未来的，灵活的选择是使用OWIN安全组件，并通过简单的配置或其他方式，允许在OWIN ASP.Net Identity组件和OWIN WS-联邦之间切换组件。

So I think to answer my question: the more future-proof and flexible choice is to use OWIN security components, and through simple configuration or other means, allow switching between the OWIN ASP.Net Identity component and the OWIN WS-Federation component.

这篇关于如何在＆QUOT; ASP.Net身份＆QUOT;与＆QUOT比较; Windows标识基础＆QUOT;？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！