I just finished implementing a custom membership provider and after the whole thing was done I'm just wondering why is it nessesary?
我刚刚实现了一个自定义成员提供程序，在整个过程完成之后，我想知道为什么是nessesary?
In my project I'm using Open ID to authenticate and once I have the users Open ID I forward them right off the bat to get OAuth request/access token then log them in using forms authentication. I'm only ever using the CreateUser() and GetUser() from the membership provider.
在我的项目中，我使用Open ID进行身份验证，一旦我让用户打开ID，我立即将它们转发给OAuth请求/访问令牌，然后使用表单身份验证登录它们。我只从成员提供程序中使用CreateUser()和GetUser()。
Can I just use my own Repository to store all of the data I need (AccessToken, Username, OpenId, etc) or is there something I'm not seeing behind the scenes that I should be aware about?
我是否可以使用我自己的存储库来存储我需要的所有数据(AccessToken，用户名，OpenId等等)，或者在我应该注意的那些场景背后是否有什么我看不到的东西?
1 个解决方案
#1
2
Yes, you can certainly use your own repository to store all the data you need. (In fact, you would use your own repository to store the information used by ASP.NET Membership.)
是的，您当然可以使用自己的存储库存储所需的所有数据。(实际上，您将使用自己的存储库存储ASP使用的信息。网会员)。
It's simply a matter of if you are willing and able to write your own code. Given that there are some security concerns, you should probably review your own design, if implemented, for security issues.
这仅仅是你是否愿意并且能够编写你自己的代码的问题。考虑到存在一些安全问题，您可能应该检查自己的设计(如果实现了)，以解决安全问题。
#1
2
Yes, you can certainly use your own repository to store all the data you need. (In fact, you would use your own repository to store the information used by ASP.NET Membership.)
是的，您当然可以使用自己的存储库存储所需的所有数据。(实际上，您将使用自己的存储库存储ASP使用的信息。网会员)。
It's simply a matter of if you are willing and able to write your own code. Given that there are some security concerns, you should probably review your own design, if implemented, for security issues.
这仅仅是你是否愿意并且能够编写你自己的代码的问题。考虑到存在一些安全问题，您可能应该检查自己的设计(如果实现了)，以解决安全问题。