jcp | 2020-01-29 15:53:55 UTC | #1
Hi, I have raised a support ticket to help with the investigation and just posting here to get some additional assistance.
A customer running the PEF (Public) is testing with the new Chrome 80 SameSite cookie features. Loading the PEF throws multiple error seen in the console log. 14:01:17.373 :1 A cookie associated with a cross-site resource at https://api.mypurecloud.ie/ was set without the SameSite attribute. It has been blocked, as Chrome now only delivers 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.
similar console messages referring to: http://apps.mypurecloud.ie/ http://mypurecloud.ie/
Are there general guidelines on investigating this ?
tim.smith | 2020-01-29 19:24:54 UTC | #2
The case with PureCloud Care is the best avenue to investigate this issue with the framework.
Travis_Cawthorn | 2020-02-03 16:18:31 UTC | #3
As you have noticed Chrome is making fairly large impacting changes round cookie enforcement for embedded pages. This change will impact the PureCloud embedded Client. Genesys has committed to providing fixes for the known and reported issues around chrome's cross site cookie enforcement.
Thanks Travis
system | 2020-03-05 16:18:33 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 7009