New commit detected on ManageIQ/manageiq-ui-classic/fine: https://github.com/ManageIQ/manageiq-ui-classic/commit/4f9a9aca911d816622685617fbe071dcbd68ca7e commit 4f9a9aca911d816622685617fbe071dcbd68ca7e Author: Martin Povolny <mpovolny> AuthorDate: Mon Apr 3 15:32:53 2017 +0200 Commit: Satoe Imaishi <simaishi> CommitDate: Tue Apr 4 09:10:28 2017 -0400 Merge pull request #410 from skateman/webmks-remote-console Support for VMware's new WebMKS HTML consoles in the UI (cherry picked from commit 5908da6121f587ce9663043d4e1e7c4bf45748d3) https://bugzilla.redhat.com/show_bug.cgi?id=1438520 app/controllers/vm_remote.rb | 17 +- .../application_helper/button/vm_webmks_console.rb | 12 + .../application_helper/toolbar/x_vm_center.rb | 8 + app/views/ops/_settings_server_tab.html.haml | 2 +- app/views/vm_common/console_webmks.html.haml | 19 + config/initializers/assets.rb | 3 + vendor/assets/images/webmks/touch_sprite.png | Bin 0 -> 24870 bytes .../assets/images/webmks/touch_sprite_feedback.png | Bin 0 -> 17962 bytes vendor/assets/javascripts/webmks.js | 6 + vendor/assets/stylesheets/webmks.scss | 661 +++++++++++++++++++++ 10 files changed, 724 insertions(+), 4 deletions(-) create mode 100644 app/helpers/application_helper/button/vm_webmks_console.rb create mode 100644 app/views/vm_common/console_webmks.html.haml create mode 100644 vendor/assets/images/webmks/touch_sprite.png create mode 100644 vendor/assets/images/webmks/touch_sprite_feedback.png create mode 100644 vendor/assets/javascripts/webmks.js create mode 100644 vendor/assets/stylesheets/webmks.scss
Tested against following Environments: 1) RHEL 7.3 - Chrome 58 - vSphere6.5 - CFME Appliance Version: 5.8.0.14-rc3 Note: Google Chrome required --ignore-certificate-errors option to be enabled and to do so, launch Google-chrome from terminal as `google-chrome --ignore-certificate-errors` Conclusion: VMware WebMKS console works 2) RHEL 7.3 - Firefox 53/52/51 - vSphere6.5 - CFME Appliance Version: 5.8.0.14-rc3 Conclusion: did NOT WORK. Tried to Use workaround: http://stackoverflow.com/questions/20088/is-there-a-way-to-make-firefox-ignore-invalid-ssl-certificates/32188658#32188658 which was mentioned in comments by martinpovolny at https://github.com/ManageIQ/manageiq-ui-classic/pull/410. (See Screenshot WebMKS_vSphere65)
Created attachment 1279782 [details] WebMKS_vSphere65
Tested against following Environments: 1) Fedora 25 - Chrome 58 - vSphere6.5 - CFME Appliance Version: 5.8.0.14-rc3 Note: Google Chrome required --ignore-certificate-errors option to be enabled and to do so, launch Google-chrome from terminal as `google-chrome --ignore-certificate-errors` Conclusion: VMware WebMKS console works 2) Fedora 25- Firefox 53/52/51 - vSphere6.5 - CFME Appliance Version: 5.8.0.14-rc3 Conclusion: did NOT WORK. Tried to Use workaround: http://stackoverflow.com/questions/20088/is-there-a-way-to-make-firefox-ignore-invalid-ssl-certificates/32188658#32188658 which was mentioned in comments by martinpovolny at https://github.com/ManageIQ/manageiq-ui-classic/pull/410.
What kind of errors are you seeing in Firefox?
David, kindly check the attachment. It shows firefox console errors. I have uploaded screenshot from RHEL but the errors appeared exactly the same on Fedora-firefox as well.
Sorry, I didn't see that. This is clearly an SSL verification issue, so it's not turned off properly. I'm not sure if FF changed the way of turning this off, or something else is wrong, it was working for me.
Tried it, FF changed its workflow a bit, but found a workaround. You should see a "Firefox can't establish a connection to wss://blablaba.blabla.bla/somethinglong" error. From this URL you need to copy the "blablabla.blabla.bla" part and paste it in a new tab with a "https://" prefix. It will open a page where you can confirm the security exception. After the security exception is confirmed, refresh the page with the remote console. Unfortunately there is no other way to do this in FF until the hypervisors' SSL certificates aren't signed by a trusted CA. AFAIK Matt Pusateri is working on this in QE's infrastructure.
Test Environments: ================== * Fedora 25- Firefox 53/52/51 and Google Chrome - vSphere6.5 - CFME Appliance Version: 5.8.0.15 * RHEL 7.3- Firefox 53/52/51 and Google Chrome- vSphere6.5 - CFME Appliance Version: 5.8.0.15 * Windows 7 - Google Chrome 58, Firefox 51/52/53 - vSphere6.0- CFME Appliance Version: 5.8.0.15 Conclusion: ============ WebMKS Console works with workaround as mentioned below. Workaround or Steps needed to make it work on Firefox or Google Chrome: ======================================================================== * Open the WebMKS VM console for the VM of your choice. * Right click on page somewhere and click Inspect Element or use key F12 and then click on Console in opened window. (Please refer screenshot attached) * There you will find the error "Firefox can't establish a connection to wss://blablaba.blabla.bla/somethinglong" error. From this URL you need to copy the "blablabla.blabla.bla" part and paste it in a new tab with a "https://" prefix. * It will open a page where you can confirm the security exception. * Then go back to the tab which was supposed to open WebMKS Remote Console and refresh it. * It should then connect to VM. ***NOTE: Using this workaround for Google Chrome will be better than running Google-chrome with --ignore-certificate-errors, because later option is more insecure. And ideally, we should not ignore certificate errors for other sites if we can just ignore this one site which we trust. ***
Also, forgot to mention in previous comment, IE 11 does not work with same work around.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1367