IMPORTANT: Potential loss of functionality of 2Ring Gadgets after upgrading Google Chrome to version 80

2Ring Gadgets for Cisco Finesse Announcement Gadgets Important

This is a very important message for all 2Ring customers whose agents or supervisors use Cisco Finesse with 2Ring Gadgets for Cisco Finesse in Google Chrome.

The upcoming release of Google Chrome (v80) is expected to break some functionality in 2Ring Gadgets for Cisco Finesse starting from v3.0 up to 4.3.5 (inclusive) for all agents and supervisors using the Google Chrome v80 and newer.

Wait, can you be more specific?

An upcoming security standard https://tools.ietf.org/html/draft-west-cookie-incrementalism-00 mandates that all cookies to third party services need to be specifically marked. This is a new standard currently in a draft phase. Google is moving to enforce this new standard by default in the upcoming version of Google Chrome v80.

Some features of the 2Ring Gadgets Suite use cookies to work. The older versions of 2Ring Gadgets that predate this upcoming standard do not mark the cookies in accordance with the new standard.

Products Affected:

• 2Ring Gadgets for Cisco Finesse 3.0 – 4.3.5 (inclusive)

Products NOT Affected

• 2Ring Gadgets for Cisco Finesse older than 3.0
• 2Ring Gadgets for Cisco Finesse 4.3.6 and newer
• 2Ring Compact Agent, all versions
• 2Ring Dashboards and Wallboards, all versions
  

There is a patch for all older versions that can be applied to avoid loss of functionality. The newest versions already implement the new standard and are not affected.

When is this happening?

Google have not announced the exact date when it will start pushing the 80 release to users – it only states, “sometime in February.”

What can I do to minimize the immediate impact?

• Contact 2Ring to Upgrade the solution / apply a patch – 2Ring.com/Support
• Temporarily block or avoid Google Chrome updates, to prevent installing the version 80.
  • Only works for environments with Active Directory and group policy
    https://support.google.com/chrome/a/answer/6350036
• Disable the new samesite settings in Chrome, if the update has been installed
  • Option 1
    • Using Google Chrome navigate to the following URL: chrome://flags/#same-site-by-default-cookies and set the option value to Disabled
    • Using Google Chrome navigate to the following URL: chrome://flags/#cookies-without-same-site-must-be-secure and set the option value to Disabled
  • Option 2
    • https://chromeenterprise.google/policies/?policy=LegacySameSiteCookieBehaviorEnabledForDomainList
• Encourage agents and supervisors to use another browser. e.g., Firefox

What should I do if I need more help? 

If you have more questions, or if you would like to schedule a support session, contact our support team: www.2Ring.com/Support