On 4 February, Google is rolling out a new security update that will change how 3rd party cookies are handled in the Chrome browser. Other browsers are more than likely to also follow suit.
You can find more information about this at the following resources:
https://www.chromestatus.com/feature/5088147346030592
https://blog.chromium.org/2019/10/developers-get-ready-for-new.html
https://web.dev/samesite-cookies-explained/
What does this mean for Khoros customers?
We are currently evaluating and testing any scenarios that could typically be affected by this change, particularly around SSO/authentication. If you are a Khoros Community customer and have any questions or concerns, we have created a thread for conversations to take place here. We’ll continue to post our findings on this blog so please subscribe to this post to stay updated.
If you wish to carry out testing yourself, you can follow the instructions below (taken from SameSite Updates)
To test whether your sites may be affected by the SameSite changes:
|
Following the Chrome update, if you do encounter any unexpected behaviour please file a ticket as per the standard Support process.
Update: 4 February 2020
Salesforce have identified that some custom integrations may stop working as a result of the Chrome 80 changes. This affects instances where our Salesforce connector is being used on the classic version of Salesforce. We are dependent on a fix being provided by Salesforce, currently due to be deployed on 15 February. Further details can be found on their help page. Customers experiencing problems are advised to switch to a different browser as a workaround.
Review release notes and updates for all of our products! Select a label to browse by product or resource type.