Avaya Communicator for Web Chrome Extension "This extension may soon no longer be supported"

[edlee321]

It seems like the current chrome extension "Avaya Communicator for Web" does not support manifest v3, and google is planning on deprecating extensions that only support manifest v2

Is Avaya planning on updating this Chrome extension so it does not loose support by June 2025?

Chrome Web Store

Add new features to your browser and personalize your browsing experience.

chromewebstore.google.com

Manifest V2 support timeline | Chrome Extensions | Chrome for Developers

Details of the Manifest V2 phase-out and end of life.

developer.chrome.com

Manifest V2 support timeline​

Understand when Manifest V2 will stop working for extensions

Latest​

October 9th 2024: an update on Manifest V2 phase-out.​

Over the last few months, we have continued with the Manifest V2 phase-out. Currently the chrome://extensions page displays a warning banner for all users of Manifest V2 extensions. Additionally, we have started disabling Manifest V2 extensions on pre-stable channels.
We will now begin disabling installed extensions still using Manifest V2 in Chrome stable. This change will be slowly rolled out over the following weeks. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time, users will still be able to turn their Manifest V2 extensions back on. Enterprises using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025. See our May 2024 blog for more context.

June 3rd 2024: the Manifest V2 phase-out begins.​

Starting on June 3rd on the Chrome Beta, Dev and Canary channels, if users still have Manifest V2 extensions installed, some will start to see a warning banner when visiting their extension management page - chrome://extensions - informing them that some (Manifest V2) extensions they have installed will soon no longer be supported. At the same time, extensions with the Featured badge that are still using Manifest V2 will lose their badge.

Upcoming​

June 2025: Chrome MV2 deprecation enterprise rollout​

Enterprises using the ExtensionManifestV2Availability policy to ensure the continued functioning of Manifest V2 extensions in their organization will have one additional year - until June 2025 - to migrate the Manifest V2 extensions in their organization. Browsers with the policy enabled won't be impacted by the rollout of the deprecation until that time.

 

[sizbut]

"Is Avaya planning on updating this Chrome extension so it does not loose support by June 2025?"

Doubt it. They announced end-of-sale and end-of-support for that product back in August 2022.

 

[edlee321]

I found a workaround to allow this extension when chrome disables support for manifest v2 extensions.

Updated: 28 May, 2024

Following Google's recent modifications to the Manifest Version 2 Timelines, we're advising all Umbrella Chromebook Client (Legacy DNS Client) and Cisco Security for Chromebook client (formerly SWG Umbrella Chromebook Client) users to activate the ExtensionManifestV2Availability policy in your Google Admin Console prior to June 2024. This is a crucial action, necessitated by Google's timeline changes. Without this update, your extensions may be disabled by Google post June 2024. By taking this step, you'll ensure the continued functionality of your Umbrella Chromebook Client & SWG Umbrella Chromebook Client until June 2025."

Here's how you can enable this policy:

1. Log into your Google Admin console.
2. Navigate to Devices > Chrome > Settings.
3. Select the parent Organizational Unit where you want to enable 'Manifest V2 extension availability' policy.
4. Under 'Users & browser settings' tab, locate the policy named Manifest V2 extension availability using the 'Filter settings' option.
   
5. Choose Manifest V2 extension availability. In the 'Configuration' dropdown menu, select 'Enable manifest V2 extensions

 

[derfloh]

This workaround will be removed in the future as well, I guess.

 

[edlee321]

I guess when this happens, i would switch to firefox