Home/ Questions/Q 557093
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T11:59:22+00:00

I already have a User table in my primary application database with an email

  • 0

I already have a User 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).

Questions:

  1. Is this a bad idea? Is it a huge can of worms to use my own DB for authentication?

  2. 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.

  3. 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?

Update

I’m still looking for a little more detail here on my third question. Do I need to write my own MembershipProvider? What changes do I need to make to my web.config file? Will the [Authorize] 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?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It’s quite simple, you need to derrive MembershipProvider and implement the ValidateUser method. Take a look at this post. I’m using custom membership provider with Postgres and MVC just fine.

    • 0