Storage Access API for Mashup
Currently we are on V8.6.1(on-prem) PRPC version using Web Mashup embedded in SalesForce. We are working on a technical approach to resolve the upcoming Google Chrome's third-party cookie restrictions which would be impacting the Mashup rendering due to disabling of Third Party cookie. We reached out to SF to get a sub-domain for pega embedded app so that Mashup would be considered as First Party but with no luck. Now we are discussing the Storage Access API approach( https://developers.google.com/privacy-sandbox/3pcd/storage-access-api). Need some suggestion on how to implement it for Web mashup. Any inputs on it is appreciated. Thanks!
***Edited by Moderator Rupashree S. to add Capability tags***
Updated: 13 Mar 2024 6:07 EDT
Pegasystems Inc.
GB
@Jey2705 did you already find the post Google Chrome has announced plans to block third-party cookies end of 2023. Pega embedded AWS CCP Screen will be impacted ?
Please note that you are using an old Pega version that is now out of support. The latest documentation about browser issues can be found here:
Pega Platform 7.4 and later releases resolve this issue. If you need to troubleshoot a potential CORB issue in Pega Platform 7.3.x and earlier releases, analyze the network trace and check the browser request to see if the access group is defined. If the access group is not defined, add script to the mashup code.
Cannot embed a mashup in a Pega application
Troubleshooting browser-specific issues with mashups
CORB error with Chrome 80 SameSite cookies
@Jey2705 did you already find the post Google Chrome has announced plans to block third-party cookies end of 2023. Pega embedded AWS CCP Screen will be impacted ?
Please note that you are using an old Pega version that is now out of support. The latest documentation about browser issues can be found here:
Pega Platform 7.4 and later releases resolve this issue. If you need to troubleshoot a potential CORB issue in Pega Platform 7.3.x and earlier releases, analyze the network trace and check the browser request to see if the access group is defined. If the access group is not defined, add script to the mashup code.
Cannot embed a mashup in a Pega application
Troubleshooting browser-specific issues with mashups
CORB error with Chrome 80 SameSite cookies
If the above article is relevant, you can log a Request a Hotfix support ticket via the MSP :
@Sam Alexander would you be able to provide some insight here?
Updated: 14 Mar 2024 7:28 EDT
CSC
US
Thanks @MarijeSchillern for your response. Not sure if this is related to CORB issue.
Actual solution options are discussed in https://docs.pega.com/bundle/platform-88/page/platform/user-experience/third-party-cookies-blocked-safari.html.
We discussed both these options with the SalesForce team where our Mashup is hosted but with no luck.
That's the reason we were going to try Storage Access API approach( https://developers.google.com/privacy-sandbox/3pcd/storage-access-api) to get the cookie first before invoking <script src ='http://sample.pega.com/prweb/PRServlet?pyActivity=pzIncludeMashupScripts'></script> which in turn calls PegaCompositeGadgetMgr that throws the error "Third party cookies must be enabled for Mashup to function."
Please let me know if my understanding is correct.
Updated: 14 Mar 2024 7:45 EDT
Pegasystems Inc.
GB
@Jey2705 I cannot find solutions for this older Pega version and I cannot provide technical support - I'm hoping other PSC users can contribute..
Solutions for Pea 8.x for users where, instead of calling pzIncludeMashupScripts, client was advised to instead call MashupScripts_86.js. The MashupScripts_86.js had the cookie check code commented out in _initAllPegaObjects.
For 7.2.1 I would recommend you check if HFIX-32936, HFIX-35035 and HFIX-35879 might help. Change will be to skip showing "confirm" button when we have mashup url and host url same. Code changes will be in "PegaCompositeGadgetMgr.js" file "isCookieConsentRequired" method.
If following the Pega 7.x documentation for the Mashup setup is not working please log a support ticket via the MSP or discuss further with Pega Consulting services.
CSC
US
Thanks @MarijeSchillern. I couldn't find the reference for MashupScripts_86.js in the application. Is that called from an activity that we can replace the existing pzIncludeMashupScripts in Mashup script src url? Appreciate your help Solutions for Pea 8.x for users where, instead of calling pzIncludeMashupScripts, client was advised to instead call MashupScripts_86.js. The MashupScripts_86.js had the cookie check code commented out in _initAllPegaObjects.