We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
Some downtime and service disruptions may be experienced.
Thanks in advance for your patience.
VMware Enhanced Authentication Plugin no longer works
-
I have run my VMware virtual console in Vivaldi for several years with no issues. After the update to Vivaldi 5.7.2921.53 I've seen a change of behavior when logging into VMware.
VMware allows login to the VC using "Windows session authentication". That involves downloading the VMware Enhanced Authentication Plugin and installing it. The plugin runs as a Windows service. By clicking a checkbox on the login screen, the login credentials are filled in from the Windows OS.
Since the update to Vivaldi that functionality no longer works. I have checked the windows service and it is running. I restarted it to confirm. I have also used the same windows credentials to manually login through Vivaldi with no issues.
To troubleshoot I have used the same functionality in Microsoft Edge, which works as it always has. I've also reset settings in Vivaldi and added a new user profile in Vivaldi.
I'd appreciate any thoughts or suggestions.
-
I'd say the next step is to create a new bug report: https://vivaldi.com/pt-pt/bugreport/
-
@pauloaguia, thanks.
I just did. I was hopeful I might get lucky and someone else had already figured this out.
-
@wstonestreet Unless I am mistaken you will see the same problem with Google Chrome (since Chrome 105), and it is apparently caused by the recent change to Chromium using an independent Certificate Root Store. (Edge is probably hardcoded to still use the Windows Root Store). This feature is now enabled by default in Chromium 110, which is why you see the issue in Vivaldi 5.7.
There is a VMware KB article about this problem. (The workaround will not be quite the same for Vivaldi, use Vivaldi/Vivaldi)
It is possible that disabling an Chromium experiment flag (which is likely going away soon) might help
This is likely something WMware will have to fix, especially since the workaround is going to go away fairly soon (According to current Chrome documention Chromium 112, which will be used by the next version of Vivaldi, will be the last Chromium version supporting the policy).
-
@yngve Thank you.
I noticed over the weekend that in the latest Vivaldi update, version 6.0.2979.15, the problem seems to have gone away. So, I consider this issue closed.Of course, with this latest update Vivaldi also dropped all my pinned sites, but I can always re-pin those.
The learning curve is universal with improvements.
I appreciate your help.
