I am having the exact same problem. I have 2 environments and one was on version 56 and one on 57. The version 56 environment allowed the client integration plugin to work as expected but the version 57 environment the plugin doesn't seem to work at all.
It's also more than just an annoyance because it doesn't allow downloading of files from the datastores through the webclient. I would also guess that it won't allow OVA deployments as that relies on the client integration plugin.
We are having the same issue with vCenter 6.5.0 and the Enhanced Authentication Plugin
Unfortunately as far as Google is concerned this would seem to be permanently broken as mentioned by JeremyLCrabtree. Digging around deeper I found a workaround on another forum; it's not great; it's not permanent; and it may raise more issues then it solves; but it can be found here: https://www.reddit.com/r/vmware/comments/5zmnia/client_integration_plugin_60_flash_25_chrome_57/
To get a permanent fix (which may not even be possible anymore) VMware will need to redesign how the Client Integration Plugin works... again... I remember when VMware decided to force the vCenter Web Client down our collective throats it was explained as being because "it takes too many resources to develop a thick client and web client, so we'd rather focus on the 'universal client' (ie web) because it's OS agnostic" I wonder if they realized they would have to develop said Web Client to support all the different browser's quirks (or maybe not as it were). Still standing by that questionable decision?
The true HTML client can't come soon enough, this current version is just horrible, slow, unreliable, buggy.
I raised a case about this. Apparently VMware are working on a fix and will be released shortly.
Excellent! Please keep us updated. I've found this to be increasingly frustrating as, apparently, I can't upload files into our datastores without the plugin.
I used Firefox for now. it works.
Vmware Internally identified the issue and working on a it.Fix for this issue will be included in upcoming update releases.
2 months on, any progress on this?
We're onto Chrome 58 now, with the exact same issue.
2 people found this helpful
I have a similar issue and have found a work around that works for me and my environment. I have found that the certificate that is self-generated with the EAP plug-in is getting rejected by Chrome, you can see this if you hit F12 and look at the "Console" and "Security" tabs.
This will work as long as the exception is remembered by Chrome. A better solution would be to regenerate the certificate with the appropriate missing information, but VMware is just telling everyone to wait for the next vCenter release.
Thanks for this, I've reproduced the steps that tim_841mentioned and managed to get the certificate to issue correctly.
I've created my own version of the MSI with the csd-openssl.cfg file modified to include the SAN section.
I've uploaded the modified MSI to save time to those who want a quick fix and the csd-openssl.cfg file for those who don't trust my MSI
I can also create a transform file if needed.
Please test it out and let me know if you have any issues
"vmware-plugin" is, apparently, not in my hosts file. (or the hosts file on any of the other machines on which I have it installed)
It's not so much that we don't trust you, it's more that VMware (support) gives the run around when trying to get these things resolved. They could easily make an official patch file (or script) that modifies the CFG, runs OpenSSL, and reapplies ICACLS. Boom! DONE! The response I get is that it will be resolved with vCenter update in June/July (which has already been affecting us for about one-two months now).
It's great that VMware has such a knowledgeable and talented community, but it's sad when I get better solutions than the support that I am paying a pretty penny for.
From what I've witnessed, there is a script on the vCenter login page that will try to make a call to 'wss://vmware-plugin:8094/?src=client&sessionId=<insertSessionIDhere>&appName=ui&version=2016'
Hit F12 and look at the "Network" tab, do you see a bunch of pending connections to that address?
The additions made by the program (EAP 6.5) were:
Have you tried adding them manually?
I can't guarantee that the same changes will work in the 6.0 branch, but I think that they use 'wss://vmware-localhost:8093/' instead.