Michal,
Thank you for your response. I know I am all over the place as I am trying to figure what
works and what doesn't. What I know so far is this. spice-web-client from eyeos
https://github.com/eyeos/spice-web-client and the forked version from flex-vdi
https://github.com/flexVDI/spice-web-client work great with an unmodified websockify proxy
and a spice enabled libvirt VM. I have tested it, and the only few things missing are USB
support, multi-monitors and file xfer. But the performance are great and can play sound
and videos. All in all those guys did an amazing work. So I am trying to take it further
and have it working with ovirt.
My first step was to try to understand how remote-viewer was connecting to ovirt. I was
able to find out that out of the console.vv file only host, port, password, tls-port and
host-subject and ca. I then tried to understand where in remote-viewer the authentication
happened and in what form. So far I have track it down to spice-gtk. I am still looking
there.
I also tried to understand how ovirt websockify version was working but not knowing for
sure that it is indeed working make it challenging. Again I don't quite understand the
steps it does to start the proxying. It seems to me that it trap the authentication and do
its own but since I don't have a client working I can't really tell. the
websockify guys say the authentication should happen on the client but when I look at the
websocket-proxy code from ovirt it seems it is happening on the proxy.
So what am I looking for is an example of a client (in whatever language) that
authenticate against ovirt so that I can test it and adapt it to spice-web-client. Any
help would be appreciated.
Here are some questions I have:
why is there a port and a tls-port? what the purpose of port? When I filter it out of
console.vv, remote-viewer is still able to work with ovirt.
What's the purpose of host-subject? How is it used? How is it sent to ovirt. Same for
password? What the protocol there?