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

From: Khaled Hussein (khaled.hussein_at_gmail.com)
Date: 11/01/05 

Date: Tue, 01 Nov 2005 01:56:24 -0800

Hello,

I guess in this case you will have to build your own membership provider
that will facilitate the same membership features and tools for your own
database... so you will have to make simple modifications in your DB just
as suitable to the membership provider that you are building.

I am posting here also some links that helps in building your own membership
provider.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/bucupro.asp
http://www.15seconds.com/issue/050216.htm
http://www.theserverside.net/articles/showarticle.tss?id=CreatingProfileProvider
http://www.devx.com/asp/Article/29256

I hope this helps.
Thanks 

--
Khaled Hussein
Graduate Teaching Assistant
College of Computing and Information Technology
Arab Academy for Science and Technology and Maritime Transport
> 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

Relevant Pages

  • Re: Replacing VS .NETs SQL Server Express Edition Integration
    ... As you said you already have an existing database that contains the ... membership structure, ... Replacing VS .NET's SQL Server Express Edition Integration ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Need to load 200 users into Form security DB
    ... membership provider" if you want to see what that entails. ... My situation is that I had a development database with some users/roles ... security database in SQL2008 with 11 tables, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Seen the Survey?
    ... paper appointment records and census returns for leaders ... I'm looking at it in many ways from someone that knows such a database ... Membership Database that I perceive no real use for nor need for. ... The task is to work with kids and get them active, ...
    (uk.rec.scouting)
  • RE: ActiveDirectory and user page Access
    ... ActiveDirectory membership is not required under Integrated windows ... ActiveDirectory membership provider to authenticate again under Integrated ... windows authentication. ...
    (microsoft.public.vsnet.general)
  • Re: What do you think about......?
    ... just posting a message on one of the Yahoo groups I moderate and I ... One thing I thought of was putting the Directory in a database. ... it could be accessed by anyone with membership to the group. ... I'm not sure if you can limit access to a feature of a group while all ...
    (rec.crafts.textiles.quilting)