Click here to Skip to main content
15,892,161 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi,

I want to implement membership provider in my site that will include more that 100K users (optimistic...),but I am new with this issue.
As I know I can use integrated ASP.NET provider (ASPNETDB.mdf) and I have some questions about it:
Is it good enough for this amount of users considering users management , performance and good security?
Can I delete some unusable generated DB tables and procedure?
Can I add/rename some fields to aspnet_Profile table?
If you have some examples please add the link.
Posted

1 solution

Using Membership is pretty much the best way to handle it, but you don't have to use the standard database if you don't want.
You can always implement your own Custom Membership Providor : http://msdn.microsoft.com/en-us/library/f1kyba5e(v=vs.100).aspx[^] and use any database type or tables you want. It's not difficult to do at all!
 
Share this answer
 
Comments
OriginalGriff 5-Mar-13 8:04am    
"Is it faster or more secure?"
Depends on how you write it! :laugh:
"Do you have an example of custom membership including password reccovery for download?"
No - password recovery is never secure. You should never store passwords in a form in which they can be recovered - hash them instead. If the user looses the password, reset it and send the new one to the registered email address. I make the new password a GUID to encourage them to change it quickly...:laugh:
sharon123456789 5-Mar-13 8:22am    
so i can understand that the integrated membership is good enough for my site:)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900