Is it possible to write a MembershipProvider in .NET for CAS Shibboleth?
相关问题
- Carriage Return (ASCII chr 13) is missing from tex
- How to store image outside of the website's ro
- 'System.Threading.ThreadAbortException' in
- Request.PathInfo issues and XSS attacks
- How to dynamically load partial view Via jquery aj
相关文章
- asp.net HiddenField控件扩展问题
- asp.net HiddenField控件扩展问题
- Asp.Net网站无法写入错误日志,测试站点可以,正是站点不行
- asp.net mvc 重定向到vue hash字符串丢失
- FormsAuthenticationTicket expires too soon
- “Dynamic operations can only be performed in homog
- What is the best way to create a lock from a web a
- Add to htmlAttributes for custom ActionLink helper
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.