KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I want to make a login system using ASP.NET (MVC). On the internet, I found some bad examples that involved SQL in Click events. Other information pointed to the ASP.NET built-in membership provider. However, I want to roll my own. I don't want to use the built-in membership provider, as it only seems to work on MS SQL, and I don't like the idea of having a few foreign tables in my database. I could probably think of something, but I need a few pointers in the right direction. It does not have to be high-security, but just regular common-sense security. And I have a few direct questions: A lot of systems seem to have the Session ID stored in a user table. I guess this is to tie a session to a user to prevent hijacking. Do check this every time a user enters a page? And what do I do if the session expires? Hashing, salting, what does it do? I know of MD5 hashing and I have used it before. But not salting. Best practices for cookies?
Tags (comma-separated)
Save Edits
Cancel