[jira] [Resolved] (GUACAMOLE-622) Allow webapp-side handling of connection errors for SSH and telnet

["Michael Jumper (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper resolved GUACAMOLE-622.
--------------------------------------
       Resolution: Done
    Fix Version/s: 2.0.0

> Allow webapp-side handling of connection errors for SSH and telnet
> ------------------------------------------------------------------
>
>                 Key: GUACAMOLE-622
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-622
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole, SSH, Telnet
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Trivial
>             Fix For: 2.0.0
>
>
> [As discussed on the mailing lists|https://lists.apache.org/thread.html/c1666f7fa40771db07d14ecb329d629abd266e831cc0c9d8c69f140a@%3Cuser.guacamole.apache.org%3E], the way that the Guacamole terminal emulator is loaded prior to actually attempting the SSH/telnet connection causes issues in handling of connection errors within the webapp:
> {quote}
> I think this may be due to the way Guacamole currently handles SSH and telnet. Unlike VNC and RDP, where no display is given to the client until the connection is established, both SSH and telnet provide a display with a terminal while waiting for the connection to happen. From the perspective of the failover socket, the connection has succeeded.
> {quote}
> This should be corrected such that, to the extent possible, the terminal emulator does not start rendering frames until the connection has actually been established. This will likely mean withholding creation of the terminal emulator until it is absolutely needed - either following successful connection or upon need of username/password prompt.
> In the case of telnet, things get slightly more complicated as the username/password prompts involved are generated by the server. Even if the password is available ahead of time, properly exposing invalid credential errors will require heuristic detection of success/failure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)