[jira] [Commented] (GUACAMOLE-443) smtp field to send mail each time a connection is triggered
[ https://issues.apache.org/jira/browse/GUACAMOLE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266161#comment-16266161 ] emma commented on GUACAMOLE-443: Hi Nick, Thanks for your answer, well unfortunately i'm not a developer and my knowledge is really, really poor ! As system engineer, iam providing and installing solution to manage enterprise network. Tutorial and sample could be a nice start to explore and try to do something by myself ;-) Many thanks to all contributors for your effort and job about Guacamole, it's such an amazing project, working so nice and so useful for many of us ! Greeting from France > smtp field to send mail each time a connection is triggered > --- > > Key: GUACAMOLE-443 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-443 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Reporter: emma >Priority: Minor > Labels: features > > Using the platform for our suppliers by providing them access to remote > maintenance, would it be possible to add an option to send an email each time > a user connects to guacamole or more precisely each time a user triggers an > RDP session, VNC, ssh? > This way we could be informed that a service provider is in the process of > remote maintenance on a particular computer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: image-2018-05-30-16-26-15-928.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection2.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection6.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection5.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection1.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection4.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection8.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
emma updated GUACAMOLE-567:
---
Attachment: Network_Connection7.png
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495262#comment-16495262
]
emma commented on GUACAMOLE-567:
Hi,
today i just build from github the release 1.0.0 with new improvements,
patches, bug fixes on my Ubuntu Server 16.04.3 LTS (GNU/Linux 4.4.0-62-generic
x86_64) with Tomcat8 and that's it, nothing more, nothing less.
This server is my test server and previously i was running github 1.0.0.
version builded March the 3rd.
So i test connection on my differents servers (2003/2008/2012) and for most of
them i notice i get during the first connection the message with logo about
"Network connection unstable" despite the fact i am testing on my local
network, not on remote through internet.
Then once im connected and Windows session is opened, i disconnect from my
Windows server and the closing session seems to hang few seconds then i get
connection error screen.
!Network_Connection1.png!
!Network_Connection2.png!
If i reconnect on the same server, this kind of message disappeared and
disconnection seems to works fine on 2003 and 2008 servers. On my 2012 server i
almost always get "Network connection unstable" and "error connection" message
on disconnect !
It looks like, if there is a long time you didn't initiate a connection on a
server, then you get "network connection unstable" message with logo, once you
made at least one successful connection then disconnect works normally without
any "connection error" screen, except on 2012 server where i almost always
encounter this "problem" and message.
Or it is like at the very first connection on a server you get message during
disconnection process
!Network_Connection4.png!
then you get the message
!Network_Connection5.png!
If i wait or click Reconnect and then cancel without logging for example, the
disconnection works fine
!Network_Connection6.png!
Made another test with a 2003 Server and first time i am connecting on with
that new version of guacamole, then i get the same behavior
!Network_Connection7.png!
!Network_Connection8.png!
It is just a test but before that "Network connection problem
acknowledgement/feedback" case, i never have this behavior during disconnection
screen !
Don't know if other testers can confirm that fact ?
Many thanks for your great job, Guacamole rocks !
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png,
> image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-487) RDP server closed connection: Forcibly disconnected.
[ https://issues.apache.org/jira/browse/GUACAMOLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339651#comment-16339651 ] emma commented on GUACAMOLE-487: Ok, i'm pretty sure there's a bug with libfreerdp on Ubuntu / Debian : https://issues.apache.org/jira/browse/GUACAMOLE-484 Will check with Centos. many thanks ! Cheers > RDP server closed connection: Forcibly disconnected. > > > Key: GUACAMOLE-487 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-487 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 0.9.14 > Environment: Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-62-generic x86_64) > on VMware 5.5 >Reporter: emma >Priority: Minor > Attachments: RDP_Disconnected_issue1.png, > RDP_Disconnected_issue2.png, RDP_Disconnected_issue3.png > > > Hi, > I'm just installing and testing 0.9.14 version on Ubuntu 16.04.3 LTS > (GNU/Linux 4.4.0-62-generic x86_64) with Tomcat8 and during my first tests i > got an error while disconnecting from RDP session from Windows 2003R2 or > Windows 2012R2 (same issues). > Once im logged onto the rdp session, then from windows GUI, start / logoff i > got an error message (Cf. first screenshot) > !RDP_Disconnected_issue1.png! > Then if i click RECONNECT, and at the Windows logging screen click CANCEL the > disconnection seems to operate properly (Cf. screenshot) > !RDP_Disconnected_issue2.png! > !RDP_Disconnected_issue3.png! > So far im using Guacamole 0.9.12 running on Ubuntu 16.04.2 LTS (GNU/Linux > 4.4.0-62-generic x86_64) and also upgrade 0.9.9 on 0.9.13 and never had this > problem. > What should i check to get Guacamole 0.9.14 running without this error > message ? > All these servers were installed and setup with the same SOP. > Thank you ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-487) RDP server closed connection: Forcibly disconnected.
[ https://issues.apache.org/jira/browse/GUACAMOLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340131#comment-16340131 ] emma commented on GUACAMOLE-487: As i saw you made correction on rdp protocol with git version, i built guacamole-server from git and test again with my 2012 R2 Server and you know what ? It works like a charm ;-D Nice job ! > RDP server closed connection: Forcibly disconnected. > > > Key: GUACAMOLE-487 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-487 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 0.9.14 > Environment: Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-62-generic x86_64) > on VMware 5.5 >Reporter: emma >Priority: Minor > Attachments: RDP_Disconnected_issue1.png, > RDP_Disconnected_issue2.png, RDP_Disconnected_issue3.png > > > Hi, > I'm just installing and testing 0.9.14 version on Ubuntu 16.04.3 LTS > (GNU/Linux 4.4.0-62-generic x86_64) with Tomcat8 and during my first tests i > got an error while disconnecting from RDP session from Windows 2003R2 or > Windows 2012R2 (same issues). > Once im logged onto the rdp session, then from windows GUI, start / logoff i > got an error message (Cf. first screenshot) > !RDP_Disconnected_issue1.png! > Then if i click RECONNECT, and at the Windows logging screen click CANCEL the > disconnection seems to operate properly (Cf. screenshot) > !RDP_Disconnected_issue2.png! > !RDP_Disconnected_issue3.png! > So far im using Guacamole 0.9.12 running on Ubuntu 16.04.2 LTS (GNU/Linux > 4.4.0-62-generic x86_64) and also upgrade 0.9.9 on 0.9.13 and never had this > problem. > What should i check to get Guacamole 0.9.14 running without this error > message ? > All these servers were installed and setup with the same SOP. > Thank you ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GUACAMOLE-507) Allow "change own password" for user account allow to modify / delete existing connections
emma created GUACAMOLE-507: -- Summary: Allow "change own password" for user account allow to modify / delete existing connections Key: GUACAMOLE-507 URL: https://issues.apache.org/jira/browse/GUACAMOLE-507 Project: Guacamole Issue Type: Bug Components: guacamole Affects Versions: 1.0.0 Environment: Ubuntu server 16.04.3, guacamole git version client and server Reporter: emma Attachments: Test_changeOwnPassword_usertab_v1.0.0.png, Test_changeOwnPassword_v1.0.0.png Testing last guacamole-client AND guacamole-server git version with TOTP extensions ON and mysql database : Allow "change own password" for user account allow to modify / delete existing connections I create a standard user "test" by cloning the default admin account "guacadmin". Then i just check box "change own password" nothing more, all other boxes are blank ! Then i connect through Guacamole with that new user "test" and try to change my password then i realized i was able to see Users and Connections tabs and access them ! While on Users tab, i cannot modified my own user profile (access denied) on connections tab i can modified OR delete existings connections ?! Then i retry with a new user created WITHOUT a clone of "guacadmin" default account, and this time it's seems to work as expected ! Worth to check that and confirm there's a security issue relating to cloning account vs creating new account ? Thank you ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GUACAMOLE-487) RDP server closed connection: Forcibly disconnected.
emma created GUACAMOLE-487: -- Summary: RDP server closed connection: Forcibly disconnected. Key: GUACAMOLE-487 URL: https://issues.apache.org/jira/browse/GUACAMOLE-487 Project: Guacamole Issue Type: Bug Components: guacamole Affects Versions: 0.9.14 Environment: Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-62-generic x86_64) on VMware 5.5 Reporter: emma Attachments: RDP_Disconnected_issue1.png, RDP_Disconnected_issue2.png, RDP_Disconnected_issue3.png Hi, I'm just installing and testing 0.9.14 version on Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-62-generic x86_64) with Tomcat8 and during my first tests i got an error while disconnecting from RDP session from Windows 2003R2 or Windows 2012R2 (same issues). Once im logged onto the rdp session, then from windows GUI, start / logoff i got an error message (Cf. first screenshot) !RDP_Disconnected_issue1.png! Then if i click RECONNECT, and at the Windows logging screen click CANCEL the disconnection seems to operate properly (Cf. screenshot) !RDP_Disconnected_issue2.png! !RDP_Disconnected_issue3.png! So far im using Guacamole 0.9.12 running on Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-62-generic x86_64) and also upgrade 0.9.9 on 0.9.13 and never had this problem. What should i check to get Guacamole 0.9.14 running without this error message ? All these servers were installed and setup with the same SOP. Thank you ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-529) Despite the fact user account is disabled, user account can access to a welcome blank screen
[ https://issues.apache.org/jira/browse/GUACAMOLE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423959#comment-16423959 ] emma commented on GUACAMOLE-529: Perfect ! Great job, many thanks. Tested today on my dev server (building from git version) and applied on my production server just by replacing the "guacamole-auth-jdbc-mysql-0.9.14.jar" extension. Work as expected. > Despite the fact user account is disabled, user account can access to a > welcome blank screen > > > Key: GUACAMOLE-529 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-529 > Project: Guacamole > Issue Type: Bug >Affects Versions: 0.9.14, 1.0.0 > Environment: Ubuntu 16.04.3, mysql, git version guacamole 1.0.0 > CentOS 7, PostgreSQL, Guacamole Client 0.9.14 > CentOS 7, SQL Server, Guacamole Client 1.0.0 (git) >Reporter: emma >Assignee: Michael Jumper >Priority: Major > Fix For: 1.0.0 > > Attachments: Account_Blank_Screen.png, Account_Disable.png > > > Hi, > I've made an upgrade from 0.9.12 to 1.0.0 git version (dev) and also an > upgrade from 0.9.14 to 1.0.0 git version (dev) everything works fine without > any issues then i realized than despite my users account were disabled i can > logon to Guacamole and access to a welcome blank screen. > I've also checked in mysql database and users account are Disabled '1'. > So far when a user account was disabled, it was unable to logon and access to > any screen. User got a message onto the logon screen like "invalid > credential" or something similar. > Guess that "issue" is probably due to developpement version but quite strange > for that module managing credential and logon. > Thank you -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GUACAMOLE-529) Despite the fact user account is disabled, user account can access to a welcome blank screen
emma created GUACAMOLE-529: -- Summary: Despite the fact user account is disabled, user account can access to a welcome blank screen Key: GUACAMOLE-529 URL: https://issues.apache.org/jira/browse/GUACAMOLE-529 Project: Guacamole Issue Type: Bug Affects Versions: 1.0.0 Environment: Ubuntu 16.04.3, mysql, git version guacamole 1.0.0 Reporter: emma Attachments: Account_Blank_Screen.png, Account_Disable.png Hi, I've made an upgrade from 0.9.12 to 1.0.0 git version (dev) and also an upgrade from 0.9.14 to 1.0.0 git version (dev) everything works fine without any issues then i realized than despite my users account were disabled i can logon to Guacamole and access to a welcome blank screen. I've also checked in mysql database and users account are Disabled '1'. So far when a user account was disabled, it was unable to logon and access to any screen. User got a message onto the logon screen like "invalid credential" or something similar. Guess that "issue" is probably due to developpement version but quite strange for that module managing credential and logon. Thank you -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-529) Despite the fact user account is disabled, user account can access to a welcome blank screen
[ https://issues.apache.org/jira/browse/GUACAMOLE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407668#comment-16407668 ] emma commented on GUACAMOLE-529: Nope ! Both using guacamole-auth-jdbc-mysql-0.9.14.jar and mysql-connector-java-5.1.45-bin.jar On my 0.9.12 upgrade to 1.0.0 git version i only used the MySQL Extension. On my 0.9.14 version upgrade to 1.0.0, i used to test the TOTP extension but by now it is not used anymore as this plugin is in developpement i am waiting for the whole complete package from the next guacamole release. The TOTP extension was only test with one account (admin user account) and not other user account as it was not working as expected ! (unable to login and get a QR code to scan...). Thanks ! > Despite the fact user account is disabled, user account can access to a > welcome blank screen > > > Key: GUACAMOLE-529 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-529 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.0.0 > Environment: Ubuntu 16.04.3, mysql, git version guacamole 1.0.0 >Reporter: emma >Priority: Major > Attachments: Account_Blank_Screen.png, Account_Disable.png > > > Hi, > I've made an upgrade from 0.9.12 to 1.0.0 git version (dev) and also an > upgrade from 0.9.14 to 1.0.0 git version (dev) everything works fine without > any issues then i realized than despite my users account were disabled i can > logon to Guacamole and access to a welcome blank screen. > I've also checked in mysql database and users account are Disabled '1'. > So far when a user account was disabled, it was unable to logon and access to > any screen. User got a message onto the logon screen like "invalid > credential" or something similar. > Guess that "issue" is probably due to developpement version but quite strange > for that module managing credential and logon. > Thank you -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-567) Network connection problem acknowledgement/feedback
[
https://issues.apache.org/jira/browse/GUACAMOLE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625882#comment-16625882
]
emma commented on GUACAMOLE-567:
Hi Michael, i've made a quick test few days ago with github version an seems
better, no such warning message during connection or disconnection process.
Sounds good :).
Still waiting the new release to deploy in production
Thank you
> Network connection problem acknowledgement/feedback
> ---
>
> Key: GUACAMOLE-567
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-567
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client, guacamole-common-js
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: Network_Connection1.png, Network_Connection2.png,
> Network_Connection4.png, Network_Connection5.png, Network_Connection6.png,
> Network_Connection7.png, Network_Connection8.png, guacd-0.9.4.txt,
> guacd-1.0.0.txt, image-2018-05-30-16-26-15-928.png, internal-error.png
>
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from
> [GUAC-1055|https://jira.glyptodon.org/browse/GUAC-1055], an issue in the JIRA
> instance used by the Guacamole project prior to its move to the ASF.*
> Comments, attachments, related issues, and history from prior to acceptance
> *may not have been copied* and can be found instead at the original issue.
> {panel}
> When Guacamole detects that the network connection is slow or hanging, it
> should acknowledge this and unobtrusively notify the user. Lacking such
> notification, slow networks or remote desktop failures look like Guacamole
> bugs, and are frequently reported as such.
> Further, the total lack of a network connection is handled within JavaScript,
> but the error code is not recognized by the Guacamole client. The unknown
> error is thus translated into a generic "An internal error has occurred ..."
> message, which is obviously incorrect:
> !internal-error.png|width=320!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-675) Unexpected Internal Error when trying to create a new group
[ https://issues.apache.org/jira/browse/GUACAMOLE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717226#comment-16717226 ] emma commented on GUACAMOLE-675: Hi Michael that's ok for me. Just supposed someone using that 1.0.0 version as production server, it means database will have to be drop and recreate as you mentionned ! Well, that is clear enough, was just sure to understand every aspect of upgrade as my running version is tagged as 0.9.14 but with 1.0.0 schema from under-dev. Regards > Unexpected Internal Error when trying to create a new group > --- > > Key: GUACAMOLE-675 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-675 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-mysql >Affects Versions: 1.0.0 > Environment: Ubuntu 16.04.3 / guacamole 1.0.0 from GitHub / >Reporter: emma >Priority: Minor > Attachments: Groups.png, Groups_CatalinaOut.png, > Groups_Schema_Update1.0.0to1.0.0.png, Guacamole_db_tables.png > > > Hi, > Updating my guacamole test server running with github version 1.0.0. > previously updated few month ago. > I just running a new update with the lastest github version, everything > during the update works fine except one thing i did notice previously during > other github upgrade version from 1.0.0 to 1.0.0. > Upgrade mysql schema database encoutered an error due guacamole table > existing. > So i guess it is link with the problem during New group creation and > "Unexpected Internel Error" cause some table missing in the database. > !Groups.png!!Groups_Schema_Update1.0.0to1.0.0.png! > What i get during my upgrade procedure when i try to update the schema > !Groups_CatalinaOut.png! > In catalina.out log about SQL error. > I am not surprise that some table doesn't exist as i cannot update mysql > database schema still in 1.0.0 (from previous upgrade) so im not sure the > schema upgrade is complete from 1.0.0 to 1.0.0 with Group management ? > !Guacamole_db_tables.png! > It seems guacamole_user_group_attribute table is missing ? > Well im not an expert but group creation not working for now. > Regards -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GUACAMOLE-675) Unexpected Internal Error when trying to create a new group
emma created GUACAMOLE-675: -- Summary: Unexpected Internal Error when trying to create a new group Key: GUACAMOLE-675 URL: https://issues.apache.org/jira/browse/GUACAMOLE-675 Project: Guacamole Issue Type: Bug Components: guacamole-auth-jdbc-mysql Affects Versions: 1.0.0 Environment: Ubuntu 16.04.3 / guacamole 1.0.0 from GitHub / Reporter: emma Attachments: Groups.png, Groups_CatalinaOut.png, Groups_Schema_Update1.0.0to1.0.0.png, Guacamole_db_tables.png Hi, Updating my guacamole test server running with github version 1.0.0. previously updated few month ago. I just running a new update with the lastest github version, everything during the update works fine except one thing i did notice previously during other github upgrade version from 1.0.0 to 1.0.0. Upgrade mysql schema database encoutered an error due guacamole table existing. So i guess it is link with the problem during New group creation and "Unexpected Internel Error" cause some table missing in the database. !Groups.png!!Groups_Schema_Update1.0.0to1.0.0.png! What i get during my upgrade procedure when i try to update the schema !Groups_CatalinaOut.png! In catalina.out log about SQL error. I am not surprise that some table doesn't exist as i cannot update mysql database schema still in 1.0.0 (from previous upgrade) so im not sure the schema upgrade is complete from 1.0.0 to 1.0.0 with Group management ? !Guacamole_db_tables.png! It seems guacamole_user_group_attribute table is missing ? Well im not an expert but group creation not working for now. Regards -- This message was sent by Atlassian JIRA (v7.6.3#76005)
