title: ASP.NET MVC authentication using custom database instead of ASPNETDB?
body: <p>I already have a <code>User</code> table in my primary application database with an email address (which will act as the user name) and a password. I would like to authenticate using my database instead of the default authentication database (ASPNETDB).</p>
  
  <p><strong>Questions:</strong></p>
  
  <ol>
  <li><p>Is this a bad idea? Is it a huge can of worms to use my own DB for authentication?</p></li>
  <li><p>How much work am I adding by doing this? I already have code for hashing the password and a query that will check if the email and password match the DB. So, I wouldn't be starting from scratch.</p></li>
  <li><p>What would I need to do to use my database instead of ASPNETDB? I'm hoping this can be described in a few simple steps, but if not, could you point me to good source?</p></li>
  </ol>
  
  <p><strong>Update</strong></p>
  
  <p><strong>I'm still looking for a little more detail here on my third question.</strong> Do I need to write my own <code>MembershipProvider</code>? What changes do I need to make to my web.config file? Will the <code>[Authorize]</code> attribute still work if I write my own solution? Can I use the automatically-generated AccountController with some minor modifications or do I basically need to rewrite the account controller from scratch?</p>