Recently I've been wondering. What's the "best practice" when it comes to creating webapps with user authentication/authorization? This may be stupid, but whatever :)
What I'm wondering is, should I just use the default provider, storing membership/profile/role data in a separate database (ASPNETDB), or should I just use this database alone and add my own custom tables?
Or perhaps, is the best way to create a custom provider? I'm not very experienced using these providers, so this may not be a good question at all, but I hope some of you can give me a good answer :-)
...
Go to the complete details ...