的MembershipProvider .NET中的CAS的Shibboleth [英] MembershipProvider in .NET for CAS Shibboleth

问题描述

是否可以使用.NET编写一个对的MembershipProvider CAS Shibboleth的？

Is it possible to write a MembershipProvider in .NET for CAS Shibboleth?

推荐答案

要更改的数据源（ES从SQL到XML）时，您通常使用自定义的MembershipProvider。通过实施的MembershipProvider可以覆盖的ProviderBase方法和变化，例如，在用户是否存在或者其存储它的成员将验证。
因此，答案是肯定的，你可以，也有一些缺点，但。成员Asp.Net通常是应用程序的一部分，并从身份验证机制（如的OpenID或Shibboleth的）在同一个域中应该运行，是不同的。这意味着，你可以用自己的的MembershipProvider 各地Shibboleth的，但你可以用具有不受此提供程序（如重置密码功能）支持的一些方法结束。具有成员资格数据提供您的应用程序侧确保你有完全控制权。您可以以管理用户/角色，登录/注销和整合Shibboleth的外部认证服务的网站使用的Asp.Net成员。先给看看如何 DotNetOpenAuth 作品。

You usually use a custom MembershipProvider when want to change the data source (es from sql to xml). By implementing a MembershipProvider you can override the Providerbase methods and change, for instance, where the Membership will verify if a user exists or where its stores it. So the answer is yes you can, there are a few drawbacks though. Membership in Asp.Net is usually part of the application and should run in the same domain, differently from an Authentication mechanism (like OpenId or Shibboleth). This means that you can wrap your MembershipProvider around Shibboleth but you could end up with having some methods that are not supported by this provider (the reset password function for instance). Having the data provider for Membership on your side of the app ensure you got full control over it. You can use the Asp.Net membership on your website in order to manage users/roles, login/logouts and integrate Shibboleth as an external authentication service. Try giving a look at how DotNetOpenAuth works.

这篇关于的MembershipProvider .NET中的CAS的Shibboleth的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！