K Khan
Feb 3, 2020
  1658
(3 votes)

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. 

References:

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

Feb 03, 2020

Comments

Vincent
Vincent Feb 3, 2020 10:56 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
K Khan Feb 4, 2020 08:37 PM

@ Vincent, thanks for your input.

Vincent
Vincent Feb 4, 2020 11:45 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
K Khan Feb 5, 2020 11:56 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
K Khan Feb 6, 2020 10:10 PM

need to report I think, A cookie associated with a cross-site resource at https://dl.episerver.net/ 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 https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

Please login to comment.
Latest blogs
Display Child Pages in Content Delivery API Response

The below example will implement an instance of IContentConverterProvider to customise the serialisation of PageData and output child pages in the...

Minesh Shah (Netcel) | Oct 4, 2022

Bring the Report Center back in Optimizely CMS 12

The Report Center has been a part of Optimizely CMS since its first debut in version 5R2 in 2008, but in CMS 12, it's removed! Don't despair! Make...

Tomas Hensrud Gulla | Oct 4, 2022 | Syndicated blog

Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Optimizely names Luminary Senior Developer, Ynze Nunnink, OMVP

Luminary Senior Developer and Optimizely Lead, Ynze Nunnink has secured the coveted position of Optimizely MVP. Earning a Platinum badge for his...

Ynze | Oct 2, 2022 | Syndicated blog