[ https://issues.apache.org/jira/browse/GUACAMOLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Couchman closed GUACAMOLE-84. ---------------------------------- Resolution: Cannot Reproduce Mostly likely this issue has been fixed in a recent version of the Guacamole Client. I've never run into it, and the version it was reported against was very old. If it's still an issue in a current version, please respond and re-open the issue. > self assigning new connection in guacamole show Error msg but still assigns > connection > -------------------------------------------------------------------------------------- > > Key: GUACAMOLE-84 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-84 > Project: Guacamole > Issue Type: Bug > Components: guacamole > Affects Versions: 0.9.9 > Environment: ubuntu 16.04, guacamole 0.9.9, tomcat8, nginx, mysql > Reporter: brian mullan > Priority: Minor > > On my guacamole I start with guacadmin acct but after creating my own ID and > giving myself all privileges I usually just delete the orig guacadmin account. > Then I configure new connections. > After the new connections are made I edit my own Guacamole User Account and > at the bottom click on all the connections I want access to. > Guacamole reports an Error when I hit SAVE... > But I have found that despite showing the error message guacamole has > actually gone ahead and given my Guacamole account access to the new > connections. -- This message was sent by Atlassian JIRA (v7.6.3#76005)