How to change default self signed ssl certificate of engine-websocket-proxy (spice html5) with commercially signed ssl certficate?

Solution In Progress - Updated -

Issue

  • To connect browser-based SPICE-HTML5 or noVNC console over SSL. The engine's Certificate Authority must be imported into the client browser. By default engine-websocket-proxy uses engine's self_singed certificate even if the certificate used by RHEV Manager is replaced with a commercially signed certificate. How to configure 'engine-websocket-proxy' to use legitimate SSL certificate?
  • How to connect to the console of the virtual machines with the SPICE HTML5 browser client (Tech Preview)? It should just work without importing it because the browser already has a commercially signed CA integrated.

Environment

  • Red Hat Virtualization 4.1
  • Red Hat Enterprise Virtualization 3.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content