guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Ramella <>
Subject Re: Question Regarding Invalid Username/Password for Linux VM's
Date Thu, 09 Jun 2016 15:21:59 GMT
Hi Mike,

Per our pervious email correspondence below, we successfully upgraded to the latest Apache
Incubator version of Guacamole, and we’re now seeing the “Password authentication failed:
Authentication failed (username/password)” message caught and logged at the guacd layer
when a bad username and/or password is entered for a Linux SSH session, however, looks like
the message is not being bubbled back up to the guac client view (the guac view turns black,
and the user cannot interact with the connection).

From what I can tell, once a bad username/password is caught at the guacd layer, the connection
to the VM is immediately disconnected, and the guac client layer receives a “User disconnected”
message, and the socket to guacd is closed.  The guac client layer does not receive the bad
username/password message.

Is there a way to show the bad username/password error on the guac client view, so that the
user can re-enter his/her username and password, and not have to reconnect to the VM?



From: Mike Jumper <>
Reply-To: "" <>
Date: Wednesday, June 1, 2016 at 2:09 PM
To: "" <>
Subject: Re: Question Regarding Invalid Username/Password for Linux VM's

On Wed, Jun 1, 2016 at 12:04 PM, Mike Jumper <<>>
On Wed, Jun 1, 2016 at 11:27 AM, Matthew Ramella <<>>

We’re testing out Guacamole for use in our business (CenturyLink), and have a quick question
regarding authentication to Linux VM’s via Guacamole.

In our scenario, for connecting to Linux VM’s via Guacamole, we’re not passing usernames
and/or password, and thus, Guacamole is prompting for username and password (which is exactly
what we’re looking for :-), however, we noticed that if we pass a bad username/password,
the Guacamole view does not provide an error message, and does not indicate that a bad username/password
was provided, but rather, the view seems to hang, and the user cannot interact with the view.
 We’re wondering if this is a bug?  Ideally, we were hoping that the view would indicate
that a bad username/password was provided, and to please try again.

Yes, this is a bug, but it should have been fixed recently:

If you can, please try building from git to see if the problem is resolved.

For reference, the original report of this issue was GUAC-1381 [1], fixed while debugging
changes for GUAC-1389 [2] (finalization of screen sharing support in the backend). The issue
is not in the Apache JIRA as it was fixed before migration to Apache Incubator was completed.

- Mike


View raw message