Troubleshooting: Chrome’s cookie behavior is causing issues in my Enterprise application

Issue: In the Chrome v80 and the Edge browsers, Google changed the default behavior for cookies from SameSite=None to SameSite=Lax. For Wizdom, this means that web parts generate a new session for each loading of a page and whenever a token expires. This can generate a lot of unnecessary resource consumption, and eventually lead to issues with filled caches and calls to SharePoint being throttled. To read more about SameSite behavior, see this explanation by Digiday.

Fix 1: Upgrade to Wizdom 6.41. In this version and onward, the web configuration encompasses this cookie behavior, so these issues do not occur.

Fix 2: Change the web configuration yourself. If you’re on Wizdom versions lower than 6.41, and do not want to upgrade just yet, you can change the web configuration to encompass the cookie behavior. See steps below. Note: These steps trigger the application to restart, which can cause Wizdom to be unavailable to your readers for a few minutes. Tos cause the least inconvenience, consider performing these steps outside of your normal business hours.

Changing the web configuration to encompass the SameSite cookie behavior:

1. Inside your Azure tenant, navigate to the Wizdom app service, and select App Service Editor (Preview).
   
   
   
2. Inside the App Service Editor, click Go.
   
   
   
   
3. A new browser tab opens, which shows all the files of the web application. Select the web config file.
   
   
   
   
   
4. Find the sessionState (normally at line 15), and add the new attribute cookieSameSite with a value of None. Beware of the casing.
   
   
   
   
   
   
5. After this, the application restarts. After reloading, the cookie behavior should no longer cause issues.