Authentication, Membership and login controls

Discussion in 'ASP .Net Security' started by Joey, Jan 15, 2008.

  1. Joey

    Joey Guest

    hi,

    microsoft guys have been so kind to create an entire framework for
    authentication and authorization in aspnet. i find this is really great and
    i thank them for this

    What i'd like to find out is the recommended practice for using this
    mechanism. in particular:

    1. the aspnetdb seems to be able to support users from multiple
    applications. Is it good practice to use a single aspnetdb for storing the
    user accounts of each application?

    2. what is the recommanded way to extend the fields of each user? i.e. if i
    have a customer database and i want my customers to login into their account
    should i link the two databases via an FK-like field? or is it better to
    implement the aspnetdb functionality within the customers database?
    Joey, Jan 15, 2008
    #1
    1. Advertising

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. brown
    Replies:
    0
    Views:
    321
    brown
    Oct 13, 2006
  2. Nathan Sokalski
    Replies:
    4
    Views:
    373
    Joe Kaplan
    Jul 21, 2008
  3. beaudetious
    Replies:
    3
    Views:
    385
    beaudetious
    Dec 29, 2005
  4. Nathan Sokalski
    Replies:
    4
    Views:
    172
    Joe Kaplan
    Jul 21, 2008
  5. Nathan Sokalski

    Books on ASP.NET Membership and the Login Controls

    Nathan Sokalski, Aug 2, 2008, in forum: ASP .Net Security
    Replies:
    1
    Views:
    661
    Misbah Arefin
    Aug 2, 2008
Loading...

Share This Page