Re: ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question

• Previous message: Khaled Hussein: "Re: ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question"
• In reply to: matt_at_mailinator.com: "ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Tue, 01 Nov 2005 03:52:04 -0800

Hello matt@mailinator.com,

have a look here - this is a good starting point for understanding the whole
provider pattern, and afterwards decide yourself if it makes sense to write
a provider, or simply migrate your code from 1.1 to 2.0
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/ASPNETProvMod_Intro.asp

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

> hello,
>
> im working on my first public-facing ASP.NET 2 website, and i have a
> question/concern about authentication integration.
>
> in ASP.NET 1.1, one would typically go w/ a "role yer own"
> webforms/database role-based model: in your db youd have a Users
> table, a RoleGroups table, a UserRoles table (see
> http://aspnet.4guysfromrolla.com/articles/082703-1.aspx).
>
> this worked well, because it hooked in directly with your typical
> Users table (UserID, UserName, Email, FirstName, LastName, etc...)
>
> in ASP.NET 2.0, one has the built-in Membership stuff, which uses its
> own SQL Server/Access database (the "ASPNETDB" datasource). and via
> Visual Studio 2005's "ASP.NET Configuration" GUI, one has many useful
> user/group management tools (add/delete role, find user, etc..!).
>
> however...i still need my custom db's User table -- as is expected,
> there are many columns i have for my users that are not in the
> MembershipUser object.
>
> herein lies the problem -- if i am to use ASP.NET 2's Authentication
> and RoleManagement funcationality (database), i am in effect
> maintaining *two* databases of users! the authentication db
> ("ASPNETDB"), and my customer db. this starts to add complication, not
> to mention data duplication. for example, if i wish to delete a user
> altogether, i must now delete the user in two different databases.
> likewise, if i wish to add a user, i have to add him in two databases
>
> another big concern is, most of my 1.1 apps use a simple Int32
> "UserID" identified column for anything related to my users --
> relationships to orders, comments/feedback, etc.. ASPNETDB has a
> UserID property, but i cant seem to retrieve it via the MemberUser
> obj. and it doesnt look like a simple indentifier int, either.
>
> so, what is the consenus, here? how best to work w/ this model shift
> between 1.1 and 2.0? how does one link their custom business-rules
> User table to the authentication User table...!?
>
> thanks,
> matt

• Previous message: Khaled Hussein: "Re: ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question"
• In reply to: matt_at_mailinator.com: "ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]