I spent a good part of yesterday reading on this subject and still feel that I am not sure where to go. I come from "minimize my" background when it comes to authentication and authorization. We never used Forms authentication, let alone a member API. If we look at our old code, we will use session variables to capture / control whether the user will be registered, etc. With this new project that I am going to undertake, I want to get us back on track with what we had to do for a start, using the tools provided by the framework.
I already have a database schema with which I will work, but it is not installed in stone; I can make changes to it if necessary. There is already a Users table in this scheme, an integer is used as the primary key. This table also has other information, such as first name and last name. I also have UserId-based foreign keys for other tables such as Phone and Address. Below I outline some of the pros and cons that come to mind.
Default provider
Arguments
- Less code.
- The ability to use all the server controls associated with it, such as Login, ChangePassword.
against
- . , CreateUserWizard, , , . , .
- (Phone, Address) UserId, GUID .
- ; . - TransactionScope, , .
, , , , .
.