asp.net mvc - FormsAuthentication.SetAuthCookie, session HighJacking and AJAX -


I understand AuthCookie, which is created with FormsAuthentication, takes care of encrypting (am I right? ) And Ath Token Once created, the token / auth cookie passes on every customer & lt; - & gt; Contact the server << p>

What do I think to prevent the token from being forced, we have to keep the site under SSL (HTTPS)

Quesetion # 1: AJAX compromises safety of our site? Will they also work under HTTPS?

Question # 2: We use IIS7.5 and some of our pages do not require a secure login; But looking at AuthCookie, I think it's best to keep everything under HTTPS. Will there be a clear demonstration flaw with this approach? What are some other disadvantages?

Cheers

Your understanding is correct ASP.NET encryption of your forms Efficient Token , Which is the value of your home cookie and prevents it from tampering, but if the virus is sent through the wire, then it is acceptable with the third party theft which leads to the session abduction.

For your specific questions:

  1. No, AJAX calls should not compromise your site's security, especially because they actually work on HTTPS needed.

  2. Yes you should run everything under HTTPS, when you have a website that requires authentication, with relatively modern computers, running under HTTPS The effect should be lowered Of course, it is always valuable when looking at your specific scenario, but in the form of a rule, the effect is a single digit percentage or less, and it is not what is generally considered to be noticeable.

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -