Views: 1331
Number of votes: 3
Average rating:

Will your site be effected in Chrome 80

Chrome 80 will treat cookies as SameSite=Lax by default if no SameSite attribute is specified and will reject insecure SameSite=None cookies.

Out of the box EPi Server's CMS website functionality isn't effected, but it might be effecting other areas of your website. e.g.

your integrations with Identity Providers using protocols such as SAML 2.0 or OpenID Connect or  analytics cookies that your web application creating as a third-party cookie or any feature depending on third party dependent cookies or if you are querying APIs from a third-party domain. 


Google announced it would end support for third-party cookies in Chrome by 2022

Feb 03, 2020

( By Vincent, 2/3/2020 10:56:02 PM)

Thank you for sharing this. 

According to MS doc, it's worth to note some forms of authentication e.g. OIDC and WS-Federation are not affected due to the differences in the how request flows (e.g. post based redirect). However applications use iframe got a lot of impact. 

K Khan
( By K Khan, 2/4/2020 8:37:45 PM)

@ Vincent, thanks for your input.

( By Vincent, 2/4/2020 11:45:47 PM)

Furthermore, my colleague and I tested Episerver OOTB functionality by explicitly enabling samesite cookie settings in Chrome, both Commerce manager and personalization portal login stopped working. 

K Khan
( By K Khan, 2/5/2020 11:56:37 AM)

For, out of the box, can we assume it's the same as QuickSilver? in this case, this might affect more clients.

K Khan
( By K Khan, 2/6/2020 10:10:15 PM)

need to report I think, A cookie associated with a cross-site resource at was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at and

Please login to comment.