[jira] [Created] (GUACAMOLE-545) Not able to login to Guacamole
Nitin Vashisth created GUACAMOLE-545:
Summary: Not able to login to Guacamole
Key: GUACAMOLE-545
URL: https://issues.apache.org/jira/browse/GUACAMOLE-545
Project: Guacamole
Issue Type: Bug
Components: guacamole, guacamole-auth-jdbc-mysql
Affects Versions: 0.9.14
Environment: Centos
Reporter: Nitin Vashisth
Fix For: 0.9.14
Hello Team,
I have installed guacamole and I have copied the necessary mysql jar's file
under
{{ /root/.guacamole/{extensions, lib}}}
also have created a guacamole.properties (mysql connection) file
But unfortunately I am not able to login over that. Also I have check the
/var/log/messages and /var/log/tomcat/catilina.out, both logs looks clean.
Help over this would be really appreciated.
Regards,
Nitin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GUACAMOLE-546) When using RDP with NLA and the remote account password has expired/must be changed, users don't get any indication
Shaun Tarves created GUACAMOLE-546:
--
Summary: When using RDP with NLA and the remote account password
has expired/must be changed, users don't get any indication
Key: GUACAMOLE-546
URL: https://issues.apache.org/jira/browse/GUACAMOLE-546
Project: Guacamole
Issue Type: Improvement
Components: guacd
Affects Versions: 0.9.14
Reporter: Shaun Tarves
Attachments: Screen Shot 2018-04-16 at 8.12.47 AM.png
When attempting to connect to a remote machine over RDP, if the user's account
password has expired or is marked as needing to be changed on next login, guacd
encounters a generic failure and we have no way of knowing why login failed.
When logging into the same machine with the standard Remote Desktop client, you
at least get an alert indicating what the problem is (see attached).
guacd logs don't offer any indication of the problem either. Please note that
NLA *is enabled* on the remote machine if that affects anything. I do not know
if this same issue exists when NLA is not enabled.
guacd log
{code:bash}
Apr 16 08:16:11 rahost guacd[1915]: Creating new client for protocol "rdp"
Apr 16 08:16:11 rahost guacd[1915]: Connection ID is
"$22f1a2fe-629d-4ae5-93a3-66a94fd136db"
Apr 16 08:16:11 rahost guacd[29684]: Security mode: ANY
Apr 16 08:16:11 rahost guacd[29684]: Resize method: none
Apr 16 08:16:11 rahost guacd[29684]: User
"@319b7690-3ecf-481a-b581-d9561abaa701" joined connection
"$22f1a2fe-629d-4ae5-93a3-
66a94fd136db" (1 users now present)
Apr 16 08:16:11 rahost guacd[29684]: Loading keymap "base"
Apr 16 08:16:11 rahost guacd[29684]: Loading keymap "en-us-qwerty"
Apr 16 08:16:12 rahost guacd[29684]: Error connecting to RDP server
Apr 16 08:16:12 rahost guacd[29684]: User
"@319b7690-3ecf-481a-b581-d9561abaa701" disconnected (0 users remain)
Apr 16 08:16:12 rahost guacd[29684]: Last user of connection
"$22f1a2fe-629d-4ae5-93a3-66a94fd136db" disconnected
Apr 16 08:16:12 rahost guacd[1915]: Connection
"$22f1a2fe-629d-4ae5-93a3-66a94fd136db" removed.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-545) Not able to login to Guacamole
[
https://issues.apache.org/jira/browse/GUACAMOLE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439705#comment-16439705
]
Michael Jumper commented on GUACAMOLE-545:
--
Please don't open a bug report if you simply have a question about Guacamole.
Use the u...@guacamole.apache.org mailing list instead:
http://guacamole.apache.org/support/#mailing-lists
Thanks.
> Not able to login to Guacamole
> --
>
> Key: GUACAMOLE-545
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-545
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacamole-auth-jdbc-mysql
>Affects Versions: 0.9.14
> Environment: Centos
>Reporter: Nitin Vashisth
>Priority: Major
> Fix For: 0.9.14
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hello Team,
> I have installed guacamole and I have copied the necessary mysql jar's file
> under
> {{ /root/.guacamole/{extensions, lib}}}
> also have created a guacamole.properties (mysql connection) file
> But unfortunately I am not able to login over that. Also I have check the
> /var/log/messages and /var/log/tomcat/catilina.out, both logs looks clean.
> Help over this would be really appreciated.
> Regards,
> Nitin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-545) Not able to login to Guacamole
[
https://issues.apache.org/jira/browse/GUACAMOLE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-545:
-
Flags: (was: Patch,Important)
Remaining Estimate: (was: 96h)
Original Estimate: (was: 96h)
Fix Version/s: (was: 0.9.14)
> Not able to login to Guacamole
> --
>
> Key: GUACAMOLE-545
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-545
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacamole-auth-jdbc-mysql
>Affects Versions: 0.9.14
> Environment: Centos
>Reporter: Nitin Vashisth
>Priority: Major
>
> Hello Team,
> I have installed guacamole and I have copied the necessary mysql jar's file
> under
> {{ /root/.guacamole/{extensions, lib}}}
> also have created a guacamole.properties (mysql connection) file
> But unfortunately I am not able to login over that. Also I have check the
> /var/log/messages and /var/log/tomcat/catilina.out, both logs looks clean.
> Help over this would be really appreciated.
> Regards,
> Nitin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GUACAMOLE-545) Not able to login to Guacamole
[
https://issues.apache.org/jira/browse/GUACAMOLE-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper closed GUACAMOLE-545.
Resolution: Invalid
> Not able to login to Guacamole
> --
>
> Key: GUACAMOLE-545
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-545
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole, guacamole-auth-jdbc-mysql
>Affects Versions: 0.9.14
> Environment: Centos
>Reporter: Nitin Vashisth
>Priority: Major
>
> Hello Team,
> I have installed guacamole and I have copied the necessary mysql jar's file
> under
> {{ /root/.guacamole/{extensions, lib}}}
> also have created a guacamole.properties (mysql connection) file
> But unfortunately I am not able to login over that. Also I have check the
> /var/log/messages and /var/log/tomcat/catilina.out, both logs looks clean.
> Help over this would be really appreciated.
> Regards,
> Nitin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GUACAMOLE-547) Guacd SSH doesn't supoort no auth for embedded devices
David Haukeness created GUACAMOLE-547:
-
Summary: Guacd SSH doesn't supoort no auth for embedded devices
Key: GUACAMOLE-547
URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
Project: Guacamole
Issue Type: Bug
Components: guacd, SSH
Affects Versions: 0.9.14
Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8 10:47:27
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Reporter: David Haukeness
Attachments: guacd_debug_fail.txt, openssh_verbose_successful
connection.txt
When connecting to embedded devices that implicitly allow SSH access guacd
fails when the authentication method is (none). The devices permit any SSH
user with no password access to the console, and then provide authentication
internally via their interactive shell.
Test cases:
# no username and no password configured: Guacamole requests both, then fails
to connect.
# username but no password: Guacamole requests password, and then fails to
connect.
# username and password: Guacamole asks for no input, and then fails to
connect.
I've attached guacd debug logs from the failed connection attempts, plus
OpenSSH (-vv) logs from a successful connection. (Files have been suitably
redacted). The bit they share in common is they both state "Authentication
(none)" but OpenSSH proceeds with the connection, while guacd terminates the
connection:
Guacd:
{code:java}
guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
guacd[100079]: DEBUG: Supported authentication methods: (null)
guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
removed.{code}
OpenSSH:
{code:java}
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentication succeeded (none).
Authenticated to 192.168.233.20 ([192.168.233.20]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-547) Add support for the "none" SSH authentication method
[
https://issues.apache.org/jira/browse/GUACAMOLE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-547:
-
Affects Version/s: (was: 0.9.14)
> Add support for the "none" SSH authentication method
>
>
> Key: GUACAMOLE-547
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
> Project: Guacamole
> Issue Type: New Feature
> Components: SSH
> Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8
> 10:47:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: David Hauk
>Priority: Minor
> Attachments: guacd_debug_fail.txt, openssh_verbose_successful
> connection.txt
>
>
> When connecting to embedded devices that implicitly allow SSH access guacd
> fails when the authentication method is (none). The devices permit any SSH
> user with no password access to the console, and then provide authentication
> internally via their interactive shell.
> Test cases:
> # no username and no password configured: Guacamole requests both, then
> fails to connect.
> # username but no password: Guacamole requests password, and then fails to
> connect.
> # username and password: Guacamole asks for no input, and then fails to
> connect.
> I've attached guacd debug logs from the failed connection attempts, plus
> OpenSSH (-vv) logs from a successful connection. (Files have been suitably
> redacted). The bit they share in common is they both state "Authentication
> (none)" but OpenSSH proceeds with the connection, while guacd terminates the
> connection:
> Guacd:
> {code:java}
> guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
> guacd[100079]: DEBUG: Supported authentication methods: (null)
> guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
> removed.{code}
> OpenSSH:
> {code:java}
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentication succeeded (none).
> Authenticated to 192.168.233.20 ([192.168.233.20]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-547) Add support for the "none" SSH authentication method
[
https://issues.apache.org/jira/browse/GUACAMOLE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-547:
-
Issue Type: New Feature (was: Bug)
> Add support for the "none" SSH authentication method
>
>
> Key: GUACAMOLE-547
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
> Project: Guacamole
> Issue Type: New Feature
> Components: SSH
> Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8
> 10:47:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: David Hauk
>Priority: Major
> Attachments: guacd_debug_fail.txt, openssh_verbose_successful
> connection.txt
>
>
> When connecting to embedded devices that implicitly allow SSH access guacd
> fails when the authentication method is (none). The devices permit any SSH
> user with no password access to the console, and then provide authentication
> internally via their interactive shell.
> Test cases:
> # no username and no password configured: Guacamole requests both, then
> fails to connect.
> # username but no password: Guacamole requests password, and then fails to
> connect.
> # username and password: Guacamole asks for no input, and then fails to
> connect.
> I've attached guacd debug logs from the failed connection attempts, plus
> OpenSSH (-vv) logs from a successful connection. (Files have been suitably
> redacted). The bit they share in common is they both state "Authentication
> (none)" but OpenSSH proceeds with the connection, while guacd terminates the
> connection:
> Guacd:
> {code:java}
> guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
> guacd[100079]: DEBUG: Supported authentication methods: (null)
> guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
> removed.{code}
> OpenSSH:
> {code:java}
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentication succeeded (none).
> Authenticated to 192.168.233.20 ([192.168.233.20]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-547) Add support for the "none" SSH authentication method
[
https://issues.apache.org/jira/browse/GUACAMOLE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-547:
-
Priority: Minor (was: Major)
> Add support for the "none" SSH authentication method
>
>
> Key: GUACAMOLE-547
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
> Project: Guacamole
> Issue Type: New Feature
> Components: SSH
> Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8
> 10:47:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: David Hauk
>Priority: Minor
> Attachments: guacd_debug_fail.txt, openssh_verbose_successful
> connection.txt
>
>
> When connecting to embedded devices that implicitly allow SSH access guacd
> fails when the authentication method is (none). The devices permit any SSH
> user with no password access to the console, and then provide authentication
> internally via their interactive shell.
> Test cases:
> # no username and no password configured: Guacamole requests both, then
> fails to connect.
> # username but no password: Guacamole requests password, and then fails to
> connect.
> # username and password: Guacamole asks for no input, and then fails to
> connect.
> I've attached guacd debug logs from the failed connection attempts, plus
> OpenSSH (-vv) logs from a successful connection. (Files have been suitably
> redacted). The bit they share in common is they both state "Authentication
> (none)" but OpenSSH proceeds with the connection, while guacd terminates the
> connection:
> Guacd:
> {code:java}
> guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
> guacd[100079]: DEBUG: Supported authentication methods: (null)
> guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
> removed.{code}
> OpenSSH:
> {code:java}
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentication succeeded (none).
> Authenticated to 192.168.233.20 ([192.168.233.20]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-547) Add support for the "none" SSH authentication method
[
https://issues.apache.org/jira/browse/GUACAMOLE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-547:
-
Summary: Add support for the "none" SSH authentication method (was: Guacd
SSH doesn't supoort no auth for embedded devices)
> Add support for the "none" SSH authentication method
>
>
> Key: GUACAMOLE-547
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
> Project: Guacamole
> Issue Type: Bug
> Components: SSH
> Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8
> 10:47:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: David Hauk
>Priority: Major
> Attachments: guacd_debug_fail.txt, openssh_verbose_successful
> connection.txt
>
>
> When connecting to embedded devices that implicitly allow SSH access guacd
> fails when the authentication method is (none). The devices permit any SSH
> user with no password access to the console, and then provide authentication
> internally via their interactive shell.
> Test cases:
> # no username and no password configured: Guacamole requests both, then
> fails to connect.
> # username but no password: Guacamole requests password, and then fails to
> connect.
> # username and password: Guacamole asks for no input, and then fails to
> connect.
> I've attached guacd debug logs from the failed connection attempts, plus
> OpenSSH (-vv) logs from a successful connection. (Files have been suitably
> redacted). The bit they share in common is they both state "Authentication
> (none)" but OpenSSH proceeds with the connection, while guacd terminates the
> connection:
> Guacd:
> {code:java}
> guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
> guacd[100079]: DEBUG: Supported authentication methods: (null)
> guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
> removed.{code}
> OpenSSH:
> {code:java}
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentication succeeded (none).
> Authenticated to 192.168.233.20 ([192.168.233.20]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-547) Add support for the "none" SSH authentication method
[
https://issues.apache.org/jira/browse/GUACAMOLE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jumper updated GUACAMOLE-547:
-
Component/s: (was: guacd)
> Add support for the "none" SSH authentication method
>
>
> Key: GUACAMOLE-547
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
> Project: Guacamole
> Issue Type: New Feature
> Components: SSH
> Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8
> 10:47:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: David Hauk
>Priority: Minor
> Attachments: guacd_debug_fail.txt, openssh_verbose_successful
> connection.txt
>
>
> When connecting to embedded devices that implicitly allow SSH access guacd
> fails when the authentication method is (none). The devices permit any SSH
> user with no password access to the console, and then provide authentication
> internally via their interactive shell.
> Test cases:
> # no username and no password configured: Guacamole requests both, then
> fails to connect.
> # username but no password: Guacamole requests password, and then fails to
> connect.
> # username and password: Guacamole asks for no input, and then fails to
> connect.
> I've attached guacd debug logs from the failed connection attempts, plus
> OpenSSH (-vv) logs from a successful connection. (Files have been suitably
> redacted). The bit they share in common is they both state "Authentication
> (none)" but OpenSSH proceeds with the connection, while guacd terminates the
> connection:
> Guacd:
> {code:java}
> guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
> guacd[100079]: DEBUG: Supported authentication methods: (null)
> guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
> removed.{code}
> OpenSSH:
> {code:java}
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentication succeeded (none).
> Authenticated to 192.168.233.20 ([192.168.233.20]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-547) Add support for the "none" SSH authentication method
[
https://issues.apache.org/jira/browse/GUACAMOLE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440143#comment-16440143
]
Michael Jumper commented on GUACAMOLE-547:
--
Relevant section from [RFC
4252|https://tools.ietf.org/html/rfc4252#section-5.2]:
{quote}
h3. 5.2. The "none" Authentication Request
A client may request a list of authentication 'method name' values that may
continue by using the "none" authentication 'method name'.
If no authentication is needed for the user, the server MUST return
SSH_MSG_USERAUTH_SUCCESS. Otherwise, the server MUST return
SSH_MSG_USERAUTH_FAILURE and MAY return with it a list of methods that may
continue in its 'authentications that can continue' value.
This 'method name' MUST NOT be listed as supported by the server.
{quote}
> Add support for the "none" SSH authentication method
>
>
> Key: GUACAMOLE-547
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-547
> Project: Guacamole
> Issue Type: New Feature
> Components: SSH
> Environment: Linux 4.13.0-1012-azure #15-Ubuntu SMP Thu Mar 8
> 10:47:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: David Hauk
>Priority: Minor
> Attachments: guacd_debug_fail.txt, openssh_verbose_successful
> connection.txt
>
>
> When connecting to embedded devices that implicitly allow SSH access guacd
> fails when the authentication method is (none). The devices permit any SSH
> user with no password access to the console, and then provide authentication
> internally via their interactive shell.
> Test cases:
> # no username and no password configured: Guacamole requests both, then
> fails to connect.
> # username but no password: Guacamole requests password, and then fails to
> connect.
> # username and password: Guacamole asks for no input, and then fails to
> connect.
> I've attached guacd debug logs from the failed connection attempts, plus
> OpenSSH (-vv) logs from a successful connection. (Files have been suitably
> redacted). The bit they share in common is they both state "Authentication
> (none)" but OpenSSH proceeds with the connection, while guacd terminates the
> connection:
> Guacd:
> {code:java}
> guacd[100079]: DEBUG: Successfully connected to host 192.168.233.20, port 22
> guacd[100079]: DEBUG: Supported authentication methods: (null)
> guacd[100066]: INFO: Connection "$abc52848-a11c-4397-a657-7c2d4bfdb5e9"
> removed.{code}
> OpenSSH:
> {code:java}
> debug1: SSH2_MSG_SERVICE_ACCEPT received
> debug1: Authentication succeeded (none).
> Authenticated to 192.168.233.20 ([192.168.233.20]:22).
> debug1: channel 0: new [client-session]
> debug2: channel 0: send open
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
