Symptom
Starting in Q1 2024, end users may face issues with their web applications when running in Chrome due to Chrome's third-party cookie deprecation.
End users could experience broken authentication flows or content sections not loading or incorrect behavior in applications.
Starting from January 4th, 2024, this will initially affect 1% of end users when using an unmanaged Chrome browser. More users will be affected over time. After Q2/24, without mitigation, affected products will break for all end users when using Chrome.
Microsoft Edge is built on Chromium. As far as it’s known, Microsoft will follow the Chrome approach shortly later.
These changes introduced by Google chrome will have a serious behavior change that will impact scenario of integration between Enterprise Portal, SRM and Catalogs (e.g. Punchout catalogs Amazon, Ariba, Staples etc.) and end users need to prepare their site for users who choose to browse without third-party cookies.
Read more...
Environment
Chrome Browser scenario where catalogs are having cross-site communications via SRM Portal, Fiori launchpad, NWBC.
- SAP Supplier Relationship Management (SRM)
- Product Catalogs, Punchout catalogs
- Google Chrome Browser
Product
Keywords
Google Chrome, EP, Portal, SRM, Catalog, Third-party cookie, phaseout, Punchout Catalog , KBA , SRM-EBP-CAT , Catalog Interface , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.