J
Joey
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?
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?