-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome Cookie Havoc #131
Comments
I'm not sure how/if the next Chrome release (Chrome v.80 supposed to be released February 4th) will affect our CSIS instance. I enabled some settings in my current Chrome v.79 (enabled "SameSite by default cookies" and "Cookies without SameSite must be secure" options via visiting Although, I never managed to run into a warning message about a cookie from our site (as @p-a-s-c-a-l mentioned above). I only received warnings for cookies from other sites (by visiting for example: https://csis.myclimateservice.eu/study/35/step/1528/view/maps) |
Nonetheless, modifying our CSIS cookies (setting the @fgeyer16 do you have an idea how we can manage/modify the cookies on a Drupal-level? |
I did not find any useful information how to set this attribute in Drupal 8. Drupal seems to be there on the safe side. If it is possible to set this in apache then I think this is the solution for the moment. Hopefully we do not catch some security hole doing so. |
What I found online for our problem was the following, which needs to be added to the Apache config file:
This works for my localhost (had to enable the headers module in my Apache, not sure how it is configured on our server) and I was able to either set None, Lax or Strict for the Though I'm not experienced with configuring Apache servers, so I'm not sure whether or not the mentioned configuration could have any possible security risk implications. |
Found an example, where this new Chrome behaviour will cause troubles: We will probably have to change the Cookie configuration on the profile.myclimateservice.eu and clarity.saver.red servers as well. |
Changed the cookie configuration on Profile. |
I did some testing. |
So, what's the current status of this issue? The Transport Application integrated on this page will yield the following warning in Chrome:
In Firefox, it isn't showing up at all. |
Should be solvable with CSP, see clarity-h2020/csis#134 (comment) |
The next release of Chrome may break our external components integrated as iFrame if they are served from a different domain that CSIS:
During development, react applications are typically served from http://localhost:3000/
This won't work any longer when the new security feature is implemented in Chrome. Thus we have to modify the cookies created by Drupal Core.
The text was updated successfully, but these errors were encountered: