Forum Moderators: coopster
1.
It's OK for 90% of our customers to log in to their application over https. User name and the hashed password will be stored in MySQL. After authentication, what do you think is the best way to check (on each page) if the user has been authenticated when browsing the site? Setting a cookie with some hashed content or just some session variable? We would rather not have to check the database for each page access.
2.
Any other concerns regarding SSL that I need to bear in mind in the situation described above?
3.
The other 10% of our customers would rather have a "direct" https link on their intranet to our site (i.e. no login) with some sort of identifier appended, e.g. [ourDomain.com...] Are there any concerns regarding this, the way the ?id is built and could I handle the further auth check as in 1. above when the user browses the site?
Again, all tips are much appreciated!
/Claes
Regarding the SSL bear in mind if the cookie is set on a secure site it won't be valid on the rest of the site so once logged in you will have to keep them on the secure site for any log in protected features.
Your third suggestion is frankly mad. This is about the worst security compromise imaginable, once someone has that URL they would be able to access the system and it wouldn't even be hacking just poor security.
Any ideas of a more secure way of obtaining 3. above...?
Thanks again
/Claes