Should I use Membership and Roles in ASP.NET 2.0

Discussion in 'ASP .Net Security' started by msnews.microsoft.com, Oct 31, 2006.

  1. Hello All,

    I did a lot of reading on this new feature from Microsoft ASP.NET 2.0, but I
    ran into a design problem. In my project the user information contains much
    more information then the information shown in the default membership and
    roles tables that are installed with SQL server.

    Therefore I need to link Asp_Tables to my own tables, but then I have an
    issue with transactions, if I delete a user, I need to delete all the User
    information in my tables as well, and that needs to be protected around a
    transaction. I don't want to use System.Transaction because my transactions
    will be promoted to DTC.

    I wonder if there is an elegant solution for this, so I can use ASP.NET
    membership and roles, but yet be able to have additional User information
    and keep everything protected.

    At this point I am starting to think that implementing my own Form
    Authentication is simply the way to go, using my tables with my design.
     
    msnews.microsoft.com, Oct 31, 2006
    #1
    1. Advertisements

  2. msnews.microsoft.com

    Jeff Dillon Guest

    Use a stored procedure?? Or a trigger?

    Either support transactions..

    Jeff
     
    Jeff Dillon, Nov 1, 2006
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.