FAQs for DG

Google Chrome 80/SameSite Update

A lot of questions have been asked about the upcoming Chrome 80 update and how it will be effected in the Evidon from Crownpeak products.  The short answer is it won't.  The attribute is used to try and prevent a cross-site forgery attack.  Meaning any cookie that a site attaches to can be triggered by a call out to that site or from another site.  Updating the samesite attribute allows you to confine the cookie to the site it was dropped on.  This will mainly effect cookies that are passing some type of possible sensitive information.

This all being said as a precautionary measure we have updated some of our UCP cookies with the samesite=lax attribute already.  Those two cookies are the Consent and Suppression cookie dropped by the tool.  These were fixed in our January 14th release.

For any additional information on the attribute please find this here.

 

https://blog.chromium.org/2019/10/developers-get-ready-for-new.html

Labels (1)
Version history
Revision #:
2 of 2
Last update:
a month ago
Updated by:
 
Looking for more?
Ask in Discussions
Developers

Peer-to-peer support  and answers on developing CMS templates, modifying privacy scripts or building integrations.

Digital Experience Management

Find answers and ask questions on content management, personalization and targeting.

Digital Quality Management

Find answers and ask questions on WCAG and SEO quality management.

Digital Governance

Find answers and ask questions on consent and monitoring solutions.