[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720038#comment-17720038
 ] 

Stephen Young commented on GUACAMOLE-1641:
------------------------------------------

Getting more eyes on the issue with a PR would be great. I have a 7.0u3
ESXi server that I would be happy to test on. I'm curious if it exhibits
the same 60 second disconnect issue. It is a standalone server that is not
supervised by vSphere though - I'm not sure yet how that factors into
things. I'm grabbing webmks tickets from the ESXi API directly and passing
the appropriate pieces to the JSON auth extension. Looking forward to
giving it a try.




> Add vSphere support to VNC protocol
> -----------------------------------
>
>                 Key: GUACAMOLE-1641
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1641
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole
>            Reporter: Mike Beynon
>            Priority: Minor
>
> vSphere bundles a VNC server into their ESXi hypervisor, and tunnels the VNC 
> protocol over a web socket to their client.  I'm working now to add support 
> to guacd to (1) take a vm object id name, (2) use the vSphere API to 
> establish a session with vCenter and request a webmks ticket, and (3) have 
> guacd connect to the appropriate ESXi server and port to setup the websocket 
> and then pass binary frames containing the VNC protocol.  The new parameters 
> for the guacd protocol will mean there's changes to guacamole-client also for 
> the webapp and the db storage for connection parameters.
> I plan to do this on the open source version.
> It's related to GUACAMOLE-591, except it will not show the entire VM catalog. 
>  Instead my changes will provide the mechanism in guacd, and later work can 
> add the catalog.
> Any suggestions how to proceed?  Things to do or things to avoid doing?
> Should I start with the latest apache or glyptodon source?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to