Red Hat Bugzilla – Bug 843397
Allow manual invocation of Spice session (without browser plugin)
Last modified: 2016-04-18 03:11:30 EDT
1. oVirt does not support activating Spice session without plugin installed.
2. oVirt Supports Spice within specific browsers Internet Explorer and Firefox only.
3. If user does not has plugin or use unsupported browser, he cannot activate Spice session manually as he is able to in Vnc alternative.
4. Vnc does supports manual invocation.
Align Spice to Vnc behavior for manual invocation.
If plugin is not detected present a dialog with the following information:
1. Spice plugin was not detected, for best integration please _download_ and install.
2. Manual invocation is possible using the following information:
a. Host: <name/ip>
b. Port: <port>
c. Password: <ticket>
d. CA: Click _here_ to download CA certificate.
Both Vnc and Spice activation can download MIME type configuration to automatically luanch Vnc/Spice client at client side without any plugin.
On Linux, an application can register to handle a URI. There might be a similar approach possbile on Windows. Currently the spice:// URI can't contain the CA, but as long as it is the same accross various connections, the user can save it once and use it again. It would make sense to have CA store that is automatically looked up in Spice client.
(In reply to comment #1)
> On Linux, an application can register to handle a URI. There might be a
> similar approach possbile on Windows. Currently the spice:// URI can't
> contain the CA, but as long as it is the same accross various connections,
> the user can save it once and use it again. It would make sense to have CA
> store that is automatically looked up in Spice client.
I thought about this alternative, however we probably want to pass more information during execution, such as device redirection.
Reuse of same URL will be likely impossible as the password is really a ticket which expires upon use or shortly after.
So I believe the MIME approach is the simplest and has the chance to the largest coverage (bug#843410).
ok, so let's concentrate on 843410 which seems to provide the complete solution.
*** This bug has been marked as a duplicate of bug 843410 ***
(In reply to comment #3)
> ok, so let's concentrate on 843410 which seems to provide the complete
> *** This bug has been marked as a duplicate of bug 843410 ***
I think that we can provide this bug for 3.1, it is all a matter of ~1 hour work for creating proper dialog, while bug#843410 is for future.
As a quick remedy for people able to install the spice xpi plugin, I suggest to include this in 3.1.
It is trivial, but allow people to access the spice console using the spice client.
Primitive but working.