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

From: Patrick.O.Ige (patrickige_at_optusnet.com.au)
Date: 11/01/05

  • Next message: Khaled Hussein: "Re: ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question" 
    Date: Tue, 1 Nov 2005 20:45:54 +1100

    I haven't really used the ASP.NET 2.0 built in Membership
    But i don't think you must use what is provided i guess you should be able
    to write your own customized one
    Patrick

    <matt@mailinator.com> wrote in message
    news:1130835070.838376.122790@g49g2000cwa.googlegroups.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
    > -- and if these tasks fail for some reason in one but not the other, it
    > seems quite messy.
    >
    > 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
    >

  • Next message: Khaled Hussein: "Re: ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question"

    Relevant Pages

    • Re: ASP.NET 2: Membership/RoleMangement vs. ASP.NET 1.1.. question
      ... provider pattern, and afterwards decide yourself if it makes sense to write ... > question/concern about authentication integration. ... > in ASP.NET 2.0, one has the built-in Membership stuff, which uses its ... i must now delete the user in two different databases. ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • RE: Finding a developer/tutor, value of MVP qualification.
      ... As someone with 23 years' experience of designing and building commercial ... databases, I can say that the MVP's who lurk around here really know their ... The application is a membership database. ... cards and numbers, so a member may have multiple membership numbers. ...
      (microsoft.public.access.adp.sqlserver)
    • Re: Membership Subscription Web Site w Payapal Integration
      ... > - but you will probably need to engage a developer familiar w/ both ... > Databases and Server side coding (for the platform your host ... > To find the best Newsgroup for FrontPage support see: ... How to have the membership entry forms linked to a managable ...
      (microsoft.public.frontpage.programming)
    • Re: NEHGS databases
      ... I've been thinking about joining, but it's *really* expensive for the ... I see they have a lot of databases online now. ... tied to Mass, Maine, Maryland, Connecticut, New York and possibly New ... considered membership and it was quite expensive then also. ...
      (soc.genealogy.computing)
    • Re: username or uid, or your own user tables?
      ... To implement a membership provider, you create a class that inherits the ... MembershipProvider abstract class from the System.Web.Security namespace ... I am writing a basic cms system to add pages to a site. ... management and not the built in asp.net user management system. ...
      (microsoft.public.dotnet.framework.aspnet)