ThingPark Wireless Tabs access problem with Chrome

Introduction

You may encounter a problem accessing DeviceManager, NeworkManager, OperatorManager or wlogger with Chrome version 80.0.3987.149 since March 2020. This comes after Chrome update, introducing a new cookie strategy.

Error messages

Device manager:
Your session has been disconnected, please logon again.

Network manager:
Your session has been disconnected, please logon again.

Wireless logger:
The connection has been refused (invalid credentials) or has timed out. Please log in again.

Operator manager:
Thing ThingPark Wireless Operator Manager has been activated because the service is not yet available for this operator. Please contact your representative to activate the service

Workaround in Chrome

In Google Chrome URL field, go to : chrome://flags/

Update "SameSite by default cookies" and set it to Disabled

This will disable this new feature, coming back to Chrome behaviour prior update of 80.0.3987.149.

Explanation

Google Chrome update to version 80.0.3987.149 comes with some cookies strategy changes :

Google Chrome v80 official version of the main update, enhance the security of web landing, adjust the third-party cookie strategy. Introduces a more stringent security classification of SameSite cookies, allowing third parties to call cookies only if HTTPS is set to None. In fact, as early as Chrome 51, SaMSIte cookies were first introduced, designed to block fake cross-site cookie requests.

This evolution will be reported in Actility Products in coming patch releases for all supported Actility Major versions :

ThingPark 5.2.2, ThingPark 6.1, ThingPark 7.0