Hi, Before filing a bug report, I'd like to get some feedback on this.
I have 2 guacamole-client installations on the same server -- one taken from GIT several months ago and another taken from GIT today. I'm using the LDAP extension in both cases. The older installation works fine except for a known bug related to how Firefox handles keystrokes (ie. if you hit ENTER right after inputing your username/password in the home page then subsequent attempts to connect to RDP/SSH/Telnet systems will behave oddly as if receiving ENTER keystrokes forever). Since this "keystroke bug" was supposedly fixed, I got a fresh copy from git today. However, when a valid LDAP user logs into Guacamole, there are NO connections available (/etc/guacamole has been left untouched), eg. with the old installation, the user would see 2 RDP and 1 Telnet connections, whereas now there's absolutely nothing in the panel. I'm attributing this "bug" to the LDAP extension because I can reproduce the same "no connection listed" scenario whether I place the "new" LDAP extension into /etc/guacamole/extensions when using either the new guacamole-client war or the older one. Likewise, if I use the "old" LDAP extension with the "new" guacamole-client war (both 1.1.0 of course) then I do get a proper connection listing when the LDAP user logs in. Incidentally however, I'm still seeing the Firefox ENTER keystroke bug here... Then I found https://issues.apache.org/jira/browse/GUACAMOLE-817 and noticed it's still in progress. In any case, in order to file a proper/useful bug report, I need to understand the logs before sending them. I searched all of my log files, but I can't see anything related to the search of the guac* config settings in both the old and the new installation. Catalina.out shows a successful LDAP user login, but I can't see anything related to grabbing the connection information. What should I search for exactly? My search filter is ldap-user-search-filter: (|(objectClass=guac*)(cn=*mygroup*)) Any ideas? Vieri --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
