The new functions provided under the Login section as well as the Role Management API are intented to automate various user management coding and use "aspnetdb" as their default database. This database is generated automatically by using "ASP.NET SQL Server Setup Wizard", which is invoked from "Visual Studio Command Prompt"
In the "aspnetdb" database, the 4 tables, namely aspnet_Membership, aspnet_Roles, aspnet_Users, aspnet_UsersInRoles, work together to implement the authorization function. The first two tables have the ID columns, that are used to relate with the last two tables. These IDs are automatically generated at each entry, independent of the names (user name and role name) entered, so that you can enter the same names plural times. Furthermore, except the last table, all the tables have the Application Id column, which records the specific application accessing the tables. Two different applications are recorded when accessed through the Visual Studio debugger and through the normal browser. Therefore, the entries through the former is not authenticated or authorized when accessed through the latter and vice versa.
As far as the Property function is concerned, it is not clear to me how it relates with the Membership function. After being authenticated by the Membership function, the entry is made into aspnet_Profile table in key/value format. However, the UserID has no relation with the authenticated UserID!! I will have to study how this table can be related with the aspnet_Membership table.