Question: I received a warning message concerning SameSite cookies, what now?
Answer:
Our main recommendation is to make sure your SDK (if any) is up-to-date.
We’ve already made some changes on the server side to address cookie handling. Depending on your configuration you may need to make some changes to cookie handling within your application. We have a document on this:
And some additional exposition here:
If you’re using recent versions of our SDKs cookie handling should generally be taken care of for you, but if you’re manually making HTTP calls you may need to confirm the cookie attributes. In any case there’s no substitute for functional testing–I strongly recommend enabling the new cookie behavior in Chrome for testing:
to test the effect of the new Chrome behavior on your site or cookies you manage, you can go to chrome://flags in Chrome 76+ and enable the “SameSite by default cookies” and “Cookies without SameSite must be secure” experiments.
Supporting Documentation:
Documentation: sameSite Cookie Attributes
Community Topic: SameSite cookie attribute changes are here!