I need to design an authentication system for my website, which is ASP.NET. I am looking through a video walk through on how to do this the standard ASP.NET way. It creates a separate small database under the app_data folder, with all of the authentication info it needs. My concern is that I want the login to check a Users table from my actual external database (still internal to the domain), which has the usernames and passwords of people that will be viewing the site, and adding, editing and deleting from that database. The user info is logically tied into this external database for fields such as "created by", "modified by" etc...
So I am concerned that this tutorial is a waste of time unless somehow, after authentication, I can use that value to identify who is writing to records in the external/main database, and identify them in terms of the User in the external/main database. Somehow, these two databases need to both have the same exact user info, which seems odd to me.
I thought about just writing to both databases and making sure the values are always identical, but something seems a little hokey about that.
Any good ideas from people who, unlike me, actually know how to do this? Thanks.