[
https://issues.apache.org/jira/browse/GUACAMOLE-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574707#comment-17574707
]
Nick Couchman commented on GUACAMOLE-1641:
------------------------------------------
[~mbeynon]: Regarding the disconnect issue, nothing specific comes to mind.
Based on what you've described it sounds like vCenter already tunnels the VNC
connection over websockets, so you're basically using the VNC protocol but
making a WS connection to get to it? Not sue on that one.
Regarding the prompt for username/password - you can prompt for this at any
time during the connection, it doesn't have to be after VNC has started its
negotiation. We did that with both VNC and RDP because it makes sense for those
two protocols - it allows Guacamole to determine what the server is asking for
and then send that back to the client, rather than trying to make assumptions
about what it may or may not want. That said, if, for the vCenter WS+VNC
protocol you need to do something different, that should be doable. Essentially
you need to establish the Guacamole connection, register the required arguments
with guac_argv_register(), send the required properties to the client with
guac_client_owner_send_required(), and then wait for the user to respond with
guac_argv_await(). You can see a couple of examples of this in the vnc auth.c
file (src/protocols/vnc/auth.c).
> 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)
