Technology Blog Posts by SAP
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

How to Test Your Solution for Breakage

JessyMonrose
Associate
Associate
‎2024 May 22 1:27 PM
2,714

Change in Progress (Update 2024-09-05)

Google has revised its strategy (July 22nd, 2024) regarding the third-party cookie deprecation. Instead of enforcing tracking protection by blocking third-party cookies centrally, they will offer this as a choice to their users across all their web browsing.

To allow our users to enable tracking protection, the solutions discussed in the blog remain fully relevant. We will update the blog accordingly and incorporate any guidance of Google as it becomes available.

Furthermore, Google announced that the grace period of the deprecation trials are prolonged indefinitely. This affects the 1% trial of the third-party cookie deprecation. We have updated our guidance on this point as well.

 

Browsers Are Ending Third-Party Cookie Support

As you may already be aware, browser manufacturers are presenting users with a choice for tracking protection that disallows third-party cookies. A prominent example is Google Chrome’s plan to let “people make an informed choice that applies across their web browsing”. This might impact your SAP solutions especially regarding session management and single sign-on authentication, as we mentioned in the first installment of our blog series. If you haven’t already, we recommend reading through it to know whether your solution is affected by the third-party cookie deprecation.

In our second installment, we’ll provide you with recommendations to prepare, test for breakage, and minimize the impact on your SAP solution.

 

Why Testing Is Important?

Cookies are used for various purposes in many applications. From session information to technical authentication flows, there are many ways an application might be affected from the phase-out of third-party cookies. Unfortunately, there is no automated way to determine whether an application is affected. However, there are three main criteria that can help you assess whether your application might be affected by the third-party cookie deprecation: An application uses (1) embedded content, which is (2) served by a third-party domain and (3) the embedded content needs cookies.

JessyMonrose_0-1723211519596.png

If one of these three criteria is not met, e.g., if your solutions are not intended to run embedded in iFrames or if or they all run on the same domain. But be aware that embedded scenarios can also occur, when using solutions like SAP Build Work Zone and be cautious before declaring your application(s) as not affected.“

Thus, we highly recommend you thoroughly test the behavior of your application simulating the tracking protection. We have come up with a proper testing guide that should help you get started with testing. For more information and the full detailed procedure, see Preparing and Testing Your Solution for Third-Party Cookie Phase-Out on the help portal.

 

How Should You Handle Chrome’s 1% Deprecation Trial?

Google Chrome is running a trial during which third-party cookies are blocked for 1% of unmanaged Chrome users. These users might be affected even though they have not opted to use the new tracking-protection feature. Our dedicated guide on the help portal, Preparing and Testing Your Solution for Third-Party Cookie Phase-Out, describes how to simulate an affected client.

Google offers a deprecation trial that businesses can apply for on a domain basis. Participation in the trial will exclude all applications hosted on approved domains from the 1% trial. Because SAP is approved for these exceptions, most notably for the domains used by SAP BTP, i.e. ondemand.com and sapcloud.cn. If your application is hosted on these domains, it is likely not affected by the 1% trial.

 

What Should You Do After Testing?

If your notice a breakage after testing, consider Google’s deprecation trial period, which allows you to opt-out of the 1% trial of the third-party cookie deprecation. Then, migrate away from third-party cookie dependencies, investigate on potential solutions for your application and implement a permanent solution. We provide more info on the deprecation trial tokens on the help page: Applying for a Deprecation Trial for the Third-Party Cookie Phase-Out.

This is the second part of our blog series covering the third-party cookie deprecation: 

Keep watching this space for more information regarding Google’s third-party cookie deprecation.