Is there an alternative method for storing user credentials / authentication repository in a website without having to store in a SQL database?
The reason I am asking is because my website hoster only allows for one MS SQL database per account, so I have a choice of either storing the membership database - ASPNETDB.MDF or the information database that I actually want to be diplayed in the webpages - Product database.
If I can't store and therefore display the product information, the website is useless. I have discovered that there is no point in putting the membership database in an App_Data folder on the site as SQL databases have to be stored in a seperate SQL Server (as seems to be the case with all the .net hosting companies I have looked at).
I really only need the site to authenticate for 3 users (1 role?) so they can update/edit information in the SQL product database via the website interface. All other users would be a ...
Go to the complete details ...