Asp.Net MVC 3 MembershipProvider 和 ClientCertificate
我正在考虑为我的网络应用程序编写自己的 MembershipProvider。人们通常不会注册，但会提供登录信息。那么会员资格难道不是正确的事情吗？
我仍然会扮演一些角色，我可能不希望人们使用 ClientCertificate 而不是正常登录进行身份验证。我仍然不希望他们进行成员身份验证（我可以使用证书和数据库中有一个可识别字段）并使用角色等。
MembershipProvider 是否可能仅用于原始登录身份验证而不是授权？
验证用户时似乎没有发生任何特殊情况，那么授权属性如何知道谁被授权了？
I was thinking about writing my own MembershipProvider for my web app. People won't normally register but will be supplied with login info. Will membership then not be the right thing?
I still will have some roles and such as well and I might wan't to be able for people to Authenticate using ClientCertificate instead of normal login. I still wan't them to be membership verified (there is a identifiable field in Certificate and Database I could use) and use roles and such.
Is MembershipProvider perhaps only used with original login Authentication and not authorization?
There doesn't seem to happen anything special when a user is validated so hwo does the authorization atrtibute know who is autorized?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您想提供登录信息，现有的会员资格就可以正常工作。 不要求用户注册必须由用户发起。只需获取标准代码并让站点管理员运行它即可。
是的，会员资格只是为了认证。开箱即用的授权功能是角色功能。
The existing membership works just fine if you want to supply login info. There is no requirement that user registration be initiated by the user. Just take the standard code and let the site administrator run it.
Yes, membership is just for authentication. The out of the box feature for authorization is the roles feature.