I've created my own membership providers and it was a good experience. One was for MySQL, and another was a dynamic provider that delegates to other providers at runtime. It's really nice being able to plug these providers into any app and configure them from the web.config.
We have been implementing and using VG for our .NET applications and so far we are happy with it. The most important benefits is that we have a central place to manage the authentication and the authorizations for all the company. We wanted everything to flow through a centralized security hub.
发布评论
评论（3）
我创建了自己的会员提供商，这是一次很好的体验。一个用于 MySQL，另一个是动态提供程序，在运行时委托给其他提供程序。能够将这些提供程序插入任何应用程序并从 web.config 进行配置真是太好了。
我需要的大部分信息都可以在这里找到：
我还实现了自定义 MembershipUser：
如何：实现自定义成员资格用户
下面是 ASP.NET 成员资格数据库架构 (ASPNETDB) 的便捷参考图.mdf）由 VS 自动生成：
这是它发布的博客文章来自：
ASP.NET 成员架构
I've created my own membership providers and it was a good experience. One was for MySQL, and another was a dynamic provider that delegates to other providers at runtime. It's really nice being able to plug these providers into any app and configure them from the web.config.
Most of the information I needed was found here:
I also implemented a custom MembershipUser:
How to: Implement a Custom Membership User
And here's a handy reference diagram of the ASP.NET Membership Database Schema (ASPNETDB.mdf) automatically generated by VS:
Here's the blog post it came from:
ASP.NET Membership Schema
我们始终实施自己的应用程序并根据需要使其安全（在某些 HIPPA 应用程序上工作）。
http://www.codeproject.com/KB/aspnet/WSSecurityProvider.aspx
http://blogs.iis.net/rakkimk/archive/2008/04/11/asp-net-using -activedirectorymembershipprovider 使用相同的加密方法来加密秘密密码答案并将其存储在 ad.aspx
We have always implemented our own and made it as secure as needed (worked on some HIPPA apps).
http://www.codeproject.com/KB/aspnet/WSSecurityProvider.aspx
http://blogs.iis.net/rakkimk/archive/2008/04/11/asp-net-using-the-same-encryption-method-used-by-activedirectorymembershipprovider-to-encrypt-secret-password-answer-and-store-it-in-ad.aspx
我们一直在为我们的 .NET 应用程序实现和使用 VG，到目前为止我们对此感到满意。
最重要的好处是我们有一个中心位置来管理所有公司的身份验证和授权。我们希望一切都通过集中式安全中心进行。
现在，有了新版本，我们计划将其应用于我们的 Java 应用程序。
我想这个链接显示了有关多种技术版本的基本信息：
http://www.visual-guard.com/EN/user-management-authentication-iam-rbac-access-control-security/identity-role-permission-audit
We have been implementing and using VG for our .NET applications and so far we are happy with it.
The most important benefits is that we have a central place to manage the authentication and the authorizations for all the company. We wanted everything to flow through a centralized security hub.
And now with the new version, we plan to implement it for our Java applications.
I guess this link shows the basic infos about the version for multi technologies:
http://www.visual-guard.com/EN/user-management-authentication-iam-rbac-access-control-security/identity-role-permission-audit