Hi Dee,
I really suggest you look into asp.net 2 (I am on a quest to let every living
soul upgrad to v2 so I maybe biased) :
New Security Features in ASP.NET 2.0
http://msdn.microsoft.com/library/en...asp?frame=true
22/08/2005 15:47:47
Securing ASP.NET Applications - With Less Code
http://msdn.microsoft.com/library/en...asp?frame=true
22/08/2005 15:46:52
New Membership Features in ASP.NET Whidbey
http://msdn.microsoft.com/library/en...asp?frame=true
22/08/2005 15:46:15
If you use v2 then:
- The choice between sql server and access is transparent (access provider
will be available after the official release but I would use sql server (express)
anyway)
- You don't write a single line of code (and as a consequence give the user
more functions like recovery, secret questions,...)
- Your solution is very safe (The passes are salted out of the box. Which
developer did this in the past? My guess is <1%)
- You will feel like an action hero and thus look cooler than your colleagues
(that's why I do it)
Cheers,
Tom Pester
Hi
I'm writing a page withing our site that requires logins. Where should
the
logins and passwords be kept? SqlServer/Access? Flat files? What are
the
options and trade offs?
Thanks.
Dee