Feature #1209
Improve VNC proxying system
| Status: | Closed | Start date: | 04/09/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Hector Sanjuan | % Done: | 100% | |
| Category: | Sunstone | |||
| Target version: | Release 3.8 | |||
| Resolution: | fixed | Pull request: |
Description
Ideally, VNC should be able to work on a standard reverse-proxy Sunstone/Selfservice install.
Related issues
Associated revisions
Feature #1209: Single VNC proxy for all connections
Taking advantage of latest developments contributed to websockify, we can now make use of multiples targets validated by a system of file-based tokens.
The stopvnc actions dissapear as we only have to close the connection. The proxy is launched at the start of Sunstone and shutdown and the end. The tokens which allow to set up the proxied connections expire after 4 seconds.
Necessary modifications have been made in Sunstone and SelfService. novnc install script has been modified to fetch the websockify proxy files from the original project. Also, only the strictly necessary files for novnc+websockify to run are now installed.
(cherry picked from commit 89631ebdb4c8a5368924cc04ddea0ebf955d75c5)
History
#1
Updated by Hector Sanjuan almost 9 years ago
- Status changed from New to Assigned
- Target version set to Release 3.8
- % Done changed from 0 to 50
#2
Updated by Hector Sanjuan almost 9 years ago
- % Done changed from 50 to 100
- Resolution set to fixed
#3
Updated by Ruben S. Montero almost 9 years ago
- Status changed from Assigned to Closed