vurthemes.blogg.se

With the recent release of Chrome 80 in February, there was a change to the way cookies are handled, this effects Punchout integrations as most systems such as SAP Ariba will present the merchants store inside of an iframe within Ariba.

Here's an outline of the main issues I faced and how to resolve them I thought it'll be worth sharing some of these to save you a day (or two) of struggling to fix them. We've integrated Magento and other procurement systems via Punchout over 10 times, so I'm used to debugging and solving the odd issue, but there was some really surprising issues that took a while to resolve. Users in a Chrome version prior to 90 could disable samesite cookies in order to avoid being impacted, however, as of version 90, samesite cookies can no longer be disabled.Debugging Issues, while Integrating Magento 2 and SAP AribaI recently had to debug issues while integrating Magento 2 and SAP Ariba with Punchout for login, cart transfer and order processing. Details on this change can be found in KBA 186196. The Chromium project made changes to how cookies are handled in winter of 2020.

Supplier uses cross site cookies, which the latest versions of Chrome and Edge Browsers are restricting.If you e nd the PunchOut catalog session and start a new PunchOut session later to complete the c atalog shopping process, the site continues with their previously created order, which includes the old session BuyerCookie information to submit to your Ariba Procurement Solution. When you start a PunchOut session in t he catalog, the supplier 's PunchOut catalog store s BuyerCookie information in the order.The session's BuyerCookie value from the POSR is not maintained on the POOM returned by the supplier.

Example: Browser was showing s1./Buyer but Browser Form Post URL was returning to /Buyer which doesn't match.The buyer's URL they're using to access the catalog is not in sync with their Advanced Front Door settings.