[jira] [Closed] (GUACAMOLE-1144) Option for guacd require client SSL certificate
[ https://issues.apache.org/jira/browse/GUACAMOLE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1144. Resolution: Duplicate I believe this is a duplicate GUACAMOLE-28, which deals with TLS mutual authentication. > Option for guacd require client SSL certificate > --- > > Key: GUACAMOLE-1144 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1144 > Project: Guacamole > Issue Type: New Feature > Components: guacd >Affects Versions: 1.2.0 >Reporter: Pat Riehecky >Priority: Minor > > Guacd is able to use SSL encryption to protect the traffic over real > networks, however, as the documentation notes - guacd does no authentication. > > This is a feature request to add support for guacd to require a client > certificate signed by a specified CA. Perhaps with some sort of DN > matchers... > > This would simplify instances where guacd is not located on the same system > as tomcat by providing privacy and authentication of the remote client. I'd > expect it to be transparent to the web application users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1144) Option for guacd require client SSL certificate
[ https://issues.apache.org/jira/browse/GUACAMOLE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1144: - Priority: Minor (was: Critical) > Option for guacd require client SSL certificate > --- > > Key: GUACAMOLE-1144 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1144 > Project: Guacamole > Issue Type: New Feature > Components: guacd >Affects Versions: 1.2.0 >Reporter: Pat Riehecky >Priority: Minor > > Guacd is able to use SSL encryption to protect the traffic over real > networks, however, as the documentation notes - guacd does no authentication. > > This is a feature request to add support for guacd to require a client > certificate signed by a specified CA. Perhaps with some sort of DN > matchers... > > This would simplify instances where guacd is not located on the same system > as tomcat by providing privacy and authentication of the remote client. I'd > expect it to be transparent to the web application users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1143) Update SAML documentation with more examples
[ https://issues.apache.org/jira/browse/GUACAMOLE-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1143: - Component/s: (was: guacamole-auth-cas) Documentation > Update SAML documentation with more examples > > > Key: GUACAMOLE-1143 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1143 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Pat Riehecky >Priority: Trivial > > The SAML authentication documentation could benefit from some example within > the doc. > > For example > The 'callback' url could have some hints provided as admins may not know the > result -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1154) Impossible to connect LDAP with AD Apache Guacamole
[ https://issues.apache.org/jira/browse/GUACAMOLE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176420#comment-17176420 ] Nick Couchman commented on GUACAMOLE-1154: -- [~Dread Marvaz]: Sorry to hear you've been having issues. However, this is not the best place to ask for support - please try the mailing list, first, unless/until we determine there actually is a bug. http://guacamole.apache.org/support/ > Impossible to connect LDAP with AD Apache Guacamole > --- > > Key: GUACAMOLE-1154 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1154 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-mysql, guacamole-auth-ldap >Affects Versions: 1.1.0 >Reporter: Martin Vazquez >Priority: Major > > Hi guys, im burned out > Been struggling with this for 3 days. and so far nothing. > Im running Guacamole on Debian 10 with Nginx as a reverse proxy, working fine. > The thing is, it's impossible to auth LDAP with AD. > I have two directories (dont know if its good or bad, just followed official > doc and other tutorials) > /etc/GUACAMOLE_HOME/ > /lib > /extensions: guacamole-auth-jdbc-mysql-1.1.0.jar / > guacamole-auth-ldap-1.1.0.jar / schema > /etc/guacamole/ > /extensions guacamole-auth-jdbc-mysql-1.1.0.jar guacamole-auth-ldap-1.1.0 > guacamole-auth-ldap-1.1.0.jar guacamole-auth-ldap-1.1.0.tar.gz > [guacamole.properties|https://guacamole.properties/] > guacamole.war > /lib > logback.xml > user-mapping.xml > In [guacamole.properties|https://guacamole.properties/] I configured LDAP > properties with these params > # LDAP properties > ldap-hostname: ad domain > ldap-port: 389 > ldap-user-base-dn:CN=Users,DC=domain,DC=local > ldap-username-attribute: CN > ldap-config-base-dn: CN=Users,DC=domain,DC=local > ldap-username-attribute: sAMAccountName > It only allows me to log in with guacadmin/guacadmin. > It's driving me nuts!! I dont know what else to read or where to search > If someone have any clue where to begin it'll be much much appreciated! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1151) Add nbproject directory to .gitignore file
[ https://issues.apache.org/jira/browse/GUACAMOLE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1151. -- Fix Version/s: 1.3.0 Resolution: Implemented > Add nbproject directory to .gitignore file > -- > > Key: GUACAMOLE-1151 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1151 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-server >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Trivial > Fix For: 1.3.0 > > > Since NetBeans has to create the "nbproject" metadata directory for C/C++ > projects, it'd be nice to add that to .gitignore so that the files don't get > checked into the git repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1147) Add support for additional LDAP properties in Docker
[ https://issues.apache.org/jira/browse/GUACAMOLE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1147: - Summary: Add support for additional LDAP properties in Docker (was: Add ldap-member-attribute-type support for Docker) > Add support for additional LDAP properties in Docker > > > Key: GUACAMOLE-1147 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1147 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker >Affects Versions: 1.2.0 >Reporter: Erwan >Priority: Minor > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Hi ! > I need to add this variable to my docker-compose file to use my ldap. > So, I think i'm not alone, so I suggest to add it. > Maybe, it will be useful to add other variable like : > ldap-dereference-aliases > ldap-follow-referrals > ldap-max-referral-hops > ldap-operation-timeout > Thanks for your work ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1147) Add support for additional LDAP properties in Docker
[ https://issues.apache.org/jira/browse/GUACAMOLE-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1147. -- Fix Version/s: 1.3.0 Resolution: Implemented > Add support for additional LDAP properties in Docker > > > Key: GUACAMOLE-1147 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1147 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker >Affects Versions: 1.2.0 >Reporter: Erwan >Priority: Minor > Fix For: 1.3.0 > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > Hi ! > I need to add this variable to my docker-compose file to use my ldap. > So, I think i'm not alone, so I suggest to add it. > Maybe, it will be useful to add other variable like : > ldap-dereference-aliases > ldap-follow-referrals > ldap-max-referral-hops > ldap-operation-timeout > Thanks for your work ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1150) Connection group permissions aren't checked correctly
[ https://issues.apache.org/jira/browse/GUACAMOLE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1150: - Priority: Minor (was: Major) > Connection group permissions aren't checked correctly > - > > Key: GUACAMOLE-1150 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1150 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.2.0 >Reporter: Quantum Hu >Priority: Minor > > Guacamole client will not show Save or Delete buttons for users who correctly > have permissions to connection groups. The issue is that for connection > groups, the client code checks for connection permissions instead of > connection group permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1150) Connection group permissions aren't checked correctly
[ https://issues.apache.org/jira/browse/GUACAMOLE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1150: - Fix Version/s: 1.3.0 > Connection group permissions aren't checked correctly > - > > Key: GUACAMOLE-1150 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1150 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.2.0 >Reporter: Quantum Hu >Priority: Minor > Fix For: 1.3.0 > > > Guacamole client will not show Save or Delete buttons for users who correctly > have permissions to connection groups. The issue is that for connection > groups, the client code checks for connection permissions instead of > connection group permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1150) Connection group permissions aren't checked correctly
[ https://issues.apache.org/jira/browse/GUACAMOLE-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1150. -- Resolution: Fixed > Connection group permissions aren't checked correctly > - > > Key: GUACAMOLE-1150 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1150 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.2.0 >Reporter: Quantum Hu >Priority: Minor > Fix For: 1.3.0 > > > Guacamole client will not show Save or Delete buttons for users who correctly > have permissions to connection groups. The issue is that for connection > groups, the client code checks for connection permissions instead of > connection group permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GUACAMOLE-919) An I/O error occurred while sending to the backend
[ https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reopened GUACAMOLE-919: - Oops...forgot about the documentation...need to review that pull request... > An I/O error occurred while sending to the backend > -- > > Key: GUACAMOLE-919 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-919 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-jdbc-postgresql >Affects Versions: 1.0.0 >Reporter: Mechanix >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.3.0 > > Attachments: image-2020-01-27-15-19-26-634.png > > > Hi, > we use guacamole with postgresql and openid extension. Guacamole and guacd is > deployed inside a k8s cluster. > For some reason, the authentication doesn't succeed sporadically; there is > only a blank page and this error message in the guacamole log: > *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping > query 'SELECT 1' failed: An I/O error occurred while sending to the backend.* > I suspect there is a weird timeout happening between guacamole and postgresql > but couldn't figure out why. > Any hints are much appreciated. Thanks > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-919) An I/O error occurred while sending to the backend
[ https://issues.apache.org/jira/browse/GUACAMOLE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-919: Component/s: Documentation > An I/O error occurred while sending to the backend > -- > > Key: GUACAMOLE-919 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-919 > Project: Guacamole > Issue Type: Bug > Components: Documentation, guacamole-auth-jdbc-postgresql >Affects Versions: 1.0.0 >Reporter: Mechanix >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.3.0 > > Attachments: image-2020-01-27-15-19-26-634.png > > > Hi, > we use guacamole with postgresql and openid extension. Guacamole and guacd is > deployed inside a k8s cluster. > For some reason, the authentication doesn't succeed sporadically; there is > only a blank page and this error message in the guacamole log: > *[pool-1-thread-1] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping > query 'SELECT 1' failed: An I/O error occurred while sending to the backend.* > I suspect there is a weird timeout happening between guacamole and postgresql > but couldn't figure out why. > Any hints are much appreciated. Thanks > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1135) MySQL SSL - Trust Store Paths Expecting URI
[
https://issues.apache.org/jira/browse/GUACAMOLE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-1135.
--
Fix Version/s: 1.3.0
Resolution: Fixed
> MySQL SSL - Trust Store Paths Expecting URI
> ---
>
> Key: GUACAMOLE-1135
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1135
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-auth-jdbc-mysql
>Affects Versions: 1.2.0
>Reporter: Richard Grime
>Priority: Minor
> Fix For: 1.3.0
>
>
> I'm seeing:
> {code:java}
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> /path/to/truststore.jks does not appear to be a valid URL.
> {code}
> It looks like the driver is expecting a URI, rather than plain file path?
> [MySQLAuthenticationProviderModule.java|https://github.com/apache/guacamole-client/pull/492/commits/721010cc14bd565a31faff14d9a020973128565c#diff-e8178383030ac1b242f3c02d548c882a]
> currently reads:
> {code:java}
> driverProperties.setProperty("trustCertificateKeyStoreUrl",
> trustStore.getAbsolutePath());
> {code}
> Is there a missing .toUri() ? (And in clientCertificateKeyStoreUrl) - or is
> there any example of how to configure this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GUACAMOLE-1151) Add nbproject directory to .gitignore file
Nick Couchman created GUACAMOLE-1151: Summary: Add nbproject directory to .gitignore file Key: GUACAMOLE-1151 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1151 Project: Guacamole Issue Type: Improvement Components: guacamole-server Reporter: Nick Couchman Assignee: Nick Couchman Since NetBeans has to create the "nbproject" metadata directory for C/C++ projects, it'd be nice to add that to .gitignore so that the files don't get checked into the git repo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GUACAMOLE-1120) CAS module causes app.js download errors
Nick Couchman created GUACAMOLE-1120: Summary: CAS module causes app.js download errors Key: GUACAMOLE-1120 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1120 Project: Guacamole Issue Type: Bug Components: guacamole-auth-cas Affects Versions: 1.2.0 Reporter: Nick Couchman Assignee: Nick Couchman Fix For: 1.3.0 When the common redirect field was implemented in 1.2.0, several components were left in the CAS module that are causing errors trying to download the app.js file when the module is enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1115) Printing problem that locks up the entire session and produces the disconnect
[
https://issues.apache.org/jira/browse/GUACAMOLE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1115:
-
Fix Version/s: (was: 1.2.0)
> Printing problem that locks up the entire session and produces the disconnect
> -
>
> Key: GUACAMOLE-1115
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1115
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Minor
>
> I found the printing problem that locks up the entire session and produces
> the disconnect.
> When connecting the Windows 2010 and printing the document in Microsoft Word,
> I encountered this problem.
> This problem isn't always produced and it's sometimes produced.
>
> So, I have analyzed the printing part of the guacamole server project.
> I have found the following issue:
> If *guac_rdp_print_job_set_state()* function is called after
> *guac_rdp_print_job_wait_for_ack()* call, this produces the lock of the
> entire session.
>
> {code:java}
> static void guac_rdp_print_job_set_state(guac_rdp_print_job* job,
> guac_rdp_print_job_state state) {
> pthread_mutex_lock(&(job->state_lock));
> /* Update stream state, signalling modification */
> job->state = state;
> pthread_cond_signal(&(job->state_modified));
> pthread_mutex_unlock(&(job->state_lock));
> }
> {code}
>
> {code:java}
> static int guac_rdp_print_job_wait_for_ack(guac_rdp_print_job* job) {
> /* Wait for ack if stream open and not yet received */
> pthread_mutex_lock(&(job->state_lock));
> if (job->state == GUAC_RDP_PRINT_JOB_WAITING_FOR_ACK)
> pthread_cond_wait(>state_modified, >state_lock);
> /* Reset state if ack received */
> int got_ack = (job->state == GUAC_RDP_PRINT_JOB_ACK_RECEIVED);
> if (got_ack)
> job->state = GUAC_RDP_PRINT_JOB_WAITING_FOR_ACK;
> /* Return whether ack was successfully received */
> pthread_mutex_unlock(&(job->state_lock));
> return got_ack;
> }
> {code}
>
> I think that this issue can produce a printing problem and a lock of the
> entire session.
> Please let me know whether my thought is correct.
>
> Thanks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GUACAMOLE-1115) Printing problem that locks up the entire session and produces the disconnect
[
https://issues.apache.org/jira/browse/GUACAMOLE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reopened GUACAMOLE-1115:
--
> Printing problem that locks up the entire session and produces the disconnect
> -
>
> Key: GUACAMOLE-1115
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1115
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Minor
> Fix For: 1.2.0
>
>
> I found the printing problem that locks up the entire session and produces
> the disconnect.
> When connecting the Windows 2010 and printing the document in Microsoft Word,
> I encountered this problem.
> This problem isn't always produced and it's sometimes produced.
>
> So, I have analyzed the printing part of the guacamole server project.
> I have found the following issue:
> If *guac_rdp_print_job_set_state()* function is called after
> *guac_rdp_print_job_wait_for_ack()* call, this produces the lock of the
> entire session.
>
> {code:java}
> static void guac_rdp_print_job_set_state(guac_rdp_print_job* job,
> guac_rdp_print_job_state state) {
> pthread_mutex_lock(&(job->state_lock));
> /* Update stream state, signalling modification */
> job->state = state;
> pthread_cond_signal(&(job->state_modified));
> pthread_mutex_unlock(&(job->state_lock));
> }
> {code}
>
> {code:java}
> static int guac_rdp_print_job_wait_for_ack(guac_rdp_print_job* job) {
> /* Wait for ack if stream open and not yet received */
> pthread_mutex_lock(&(job->state_lock));
> if (job->state == GUAC_RDP_PRINT_JOB_WAITING_FOR_ACK)
> pthread_cond_wait(>state_modified, >state_lock);
> /* Reset state if ack received */
> int got_ack = (job->state == GUAC_RDP_PRINT_JOB_ACK_RECEIVED);
> if (got_ack)
> job->state = GUAC_RDP_PRINT_JOB_WAITING_FOR_ACK;
> /* Return whether ack was successfully received */
> pthread_mutex_unlock(&(job->state_lock));
> return got_ack;
> }
> {code}
>
> I think that this issue can produce a printing problem and a lock of the
> entire session.
> Please let me know whether my thought is correct.
>
> Thanks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1115) Printing problem that locks up the entire session and produces the disconnect
[
https://issues.apache.org/jira/browse/GUACAMOLE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-1115.
Resolution: Invalid
> Printing problem that locks up the entire session and produces the disconnect
> -
>
> Key: GUACAMOLE-1115
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1115
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Minor
>
> I found the printing problem that locks up the entire session and produces
> the disconnect.
> When connecting the Windows 2010 and printing the document in Microsoft Word,
> I encountered this problem.
> This problem isn't always produced and it's sometimes produced.
>
> So, I have analyzed the printing part of the guacamole server project.
> I have found the following issue:
> If *guac_rdp_print_job_set_state()* function is called after
> *guac_rdp_print_job_wait_for_ack()* call, this produces the lock of the
> entire session.
>
> {code:java}
> static void guac_rdp_print_job_set_state(guac_rdp_print_job* job,
> guac_rdp_print_job_state state) {
> pthread_mutex_lock(&(job->state_lock));
> /* Update stream state, signalling modification */
> job->state = state;
> pthread_cond_signal(&(job->state_modified));
> pthread_mutex_unlock(&(job->state_lock));
> }
> {code}
>
> {code:java}
> static int guac_rdp_print_job_wait_for_ack(guac_rdp_print_job* job) {
> /* Wait for ack if stream open and not yet received */
> pthread_mutex_lock(&(job->state_lock));
> if (job->state == GUAC_RDP_PRINT_JOB_WAITING_FOR_ACK)
> pthread_cond_wait(>state_modified, >state_lock);
> /* Reset state if ack received */
> int got_ack = (job->state == GUAC_RDP_PRINT_JOB_ACK_RECEIVED);
> if (got_ack)
> job->state = GUAC_RDP_PRINT_JOB_WAITING_FOR_ACK;
> /* Return whether ack was successfully received */
> pthread_mutex_unlock(&(job->state_lock));
> return got_ack;
> }
> {code}
>
> I think that this issue can produce a printing problem and a lock of the
> entire session.
> Please let me know whether my thought is correct.
>
> Thanks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1089) Ubuntu 18.04 & last freerdp2-dev package update
[ https://issues.apache.org/jira/browse/GUACAMOLE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1089. Resolution: Invalid > Ubuntu 18.04 & last freerdp2-dev package update > --- > > Key: GUACAMOLE-1089 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1089 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Pierre-Arnaud Laporte >Priority: Minor > > Hello, > > A recent update to the freerdp2-dev (2.1.1) package on Ubuntu has broken the > Guacamole compatibilty. > RDP connection is instantly closed without any error message. > I had to downgrade to 2.0.0 to make it work again. > > Not sure if this should be there, but, as you advice to install this package > in your doc, I think, you should be aware of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1089) Ubuntu 18.04 & last freerdp2-dev package update
[ https://issues.apache.org/jira/browse/GUACAMOLE-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148823#comment-17148823 ] Nick Couchman commented on GUACAMOLE-1089: -- This continues to seem like an upstream issues with FreeRDP 2.1.1. I don't know if the distributions have released packages, yet, for 2.1.2, but it'll be interesting to see if the issues persist in that version and beyond. As Mike mentioned, it's possible something changed in 2.1.1 that caused an incompatibility, but hard to say for sure. > Ubuntu 18.04 & last freerdp2-dev package update > --- > > Key: GUACAMOLE-1089 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1089 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Pierre-Arnaud Laporte >Priority: Minor > > Hello, > > A recent update to the freerdp2-dev (2.1.1) package on Ubuntu has broken the > Guacamole compatibilty. > RDP connection is instantly closed without any error message. > I had to downgrade to 2.0.0 to make it work again. > > Not sure if this should be there, but, as you advice to install this package > in your doc, I think, you should be aware of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1119) Unable to query list of objects from LDAP directory
[ https://issues.apache.org/jira/browse/GUACAMOLE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1119: - Priority: Minor (was: Major) > Unable to query list of objects from LDAP directory > --- > > Key: GUACAMOLE-1119 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1119 > Project: Guacamole > Issue Type: Bug > Components: guacamole, guacamole-auth-ldap >Affects Versions: 1.2.0 > Environment: guacamole 1.2.0, guacd 1.2.0 running in a docker > container on Ubuntu Linux talking to Azure ADDS for secure LDAP >Reporter: Ed Withers >Priority: Minor > > We run guacamole in a docker container on an Ubuntu Linux machine. We use > Postgres for the database and secure LDAP for authentication connecting to > Azure Active Directory Domain Services. We have been running this > configuration with version 1.1.0 of guacamole and guac_d since at least last > August. The update to 1.2.0 broke that integration. > Symptom: User attempts to log in, after entering username and password, there > is a long delay and then the error "Unable to query list of objects from LDAP > directory" appears at the top of the screen and the user remains at the login > page. > docker logs show that the user successfully authenticated. > tcpdump shows traffic flowing between the guacamole container and the LDAP > server. > Reverting back to version 1.1.0 "solved" the problem. > We suspect that the new LDAP configuration options changed a default behavior > to something that is incompatible with the Azure ADDS schema. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GUACAMOLE-1122) Fail in compile of RDP protocol when SSH is unavailable
Nick Couchman created GUACAMOLE-1122: Summary: Fail in compile of RDP protocol when SSH is unavailable Key: GUACAMOLE-1122 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1122 Project: Guacamole Issue Type: Bug Components: RDP Affects Versions: 1.2.0 Reporter: Nick Couchman Assignee: Nick Couchman Fix For: 1.3.0 As reported on the mailing list [1], when SSH support is disabled RDP will fail to compile due to a variable scope issue with the settings in the file redirection portion of RDP. [1] - http://mail-archives.apache.org/mod_mbox/guacamole-user/202007.mbox/%3CCALKeL-PHdDQYjSp0MyivmE9dwhv3a02k%2By839oQtDeho8bb6-A%40mail.gmail.com%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-852) Support MariaDB JDBC Driver
[ https://issues.apache.org/jira/browse/GUACAMOLE-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153163#comment-17153163 ] Nick Couchman commented on GUACAMOLE-852: - [~scratchi]: Yes, it has been implemented. Please see release notes & documentation: http://guacamole.apache.org/releases/1.2.0/ http://guacamole.apache.org/doc/gug/jdbc-auth.html You need the "mysql-driver" property, which is documented in the manual. Please direct further questions to the mailing list: http://guacamole.apache.org/support/ > Support MariaDB JDBC Driver > --- > > Key: GUACAMOLE-852 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-852 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc-mysql >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > The MariaDB JDBC driver implements a different class than the MySQL driver, > so some changes will need to be made to the JDBC module to support that > version of the driver. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1131) "Communications link failure" after a while
[
https://issues.apache.org/jira/browse/GUACAMOLE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154487#comment-17154487
]
Nick Couchman commented on GUACAMOLE-1131:
--
[~antoine-roux]: Please start by asking for help on the mailing list:
http://guacamole.apache.org/support/
http://guacamole.apache.org/faq/#probably-not-a-bug
> "Communications link failure" after a while
> ---
>
> Key: GUACAMOLE-1131
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1131
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc
>Affects Versions: 1.2.0
> Environment: Docker
>Reporter: Antoine
>Priority: Major
>
> Hello,
> Since I upgraded to Guacamole 1.2.0 on my Docker infrastructure, I have an
> error preventing the webpage to be displayed after a while (~1h). The server
> works for a bit, then the error appears. The /guacamole/api/tokens endpoint
> never respond.
> {noformat}
> ==> /usr/local/tomcat/logs/catalina.2020-07-09.log <==
> 09-Jul-2020 12:03:36.527 WARNING [http-nio-8080-exec-8]
> org.apache.ibatis.logging.jdk14.Jdk14LoggingImpl.warn Execution of ping query
> 'SELECT 1' failed: Communications link failure
> The last packet successfully received from the server was 2,872,642
> milliseconds ago. The last packet sent successfully to the server was
> 927,976 milliseconds ago.
> {noformat}
> I can ping the DB from the guacamole container, and a restart solve the issue
> for ~1h, sometime less...
> I use OpenID and JDBC pluggin
> Thank in advance,
> Antoine
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1120) CAS module causes app.js download errors
[ https://issues.apache.org/jira/browse/GUACAMOLE-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1120. -- Resolution: Fixed > CAS module causes app.js download errors > > > Key: GUACAMOLE-1120 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1120 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-cas >Affects Versions: 1.2.0 >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.3.0 > > > When the common redirect field was implemented in 1.2.0, several components > were left in the CAS module that are causing errors trying to download the > app.js file when the module is enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1110) Size and security improvements for Docker images
[ https://issues.apache.org/jira/browse/GUACAMOLE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1110. -- Resolution: Implemented > Size and security improvements for Docker images > > > Key: GUACAMOLE-1110 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1110 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-server >Reporter: Mathias >Priority: Trivial > Labels: Docker, dockerfile > Fix For: 1.3.0 > > > Higher Security: It is best practice to run a daemon as non privileged user. > Health check: Docker can detect if a container is still working. > Docker image size: Not all recommended packages must be installed for the > final image. This small improvement can reduce the size by 200 MB. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GUACAMOLE-1123) Standardize on filtered history query for user and connection management
Nick Couchman created GUACAMOLE-1123: Summary: Standardize on filtered history query for user and connection management Key: GUACAMOLE-1123 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1123 Project: Guacamole Issue Type: Improvement Components: guacamole-auth-jdbc Reporter: Nick Couchman When querying connection history, there are several disparate endpoints that are used to gather that history. Instead of maintaining these various interfaces, we should standardize on a single connection history endpoint and update all of the relevant REST calls within the AngularJS application to reference those calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1124) TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation
[ https://issues.apache.org/jira/browse/GUACAMOLE-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1124. Resolution: Invalid The string is definitely there - I've verified both in the Git repo for the master branch as well as the 1.2.0, 1.1.0, and 1.0.0 tags. I also downloaded the guacamole-client-1.2.0.tar.gz file and have verified its presence there, as well: > TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation > -- > > Key: GUACAMOLE-1124 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1124 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.1.0, 1.2.0 >Reporter: Tim Worcester >Priority: Minor > Attachments: image-2020-07-03-12-31-46-463.png > > > I can't seem to find TEXT_CLIENT_STATUS_UNSTABLE in en.json > !image-2020-07-03-12-31-46-463.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1124) TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation
[
https://issues.apache.org/jira/browse/GUACAMOLE-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151082#comment-17151082
]
Nick Couchman commented on GUACAMOLE-1124:
--
{code:bash}
[root@ussalxapps005t guacamole-client-1.2.0]# find . -type f -iname en.json
-exec grep -H CLIENT_STATUS_UNSTABLE {} \;
./guacamole/src/main/webapp/translations/en.json:
"TEXT_CLIENT_STATUS_UNSTABLE" : "The network connection to the Guacamole
server appears unstable."
{code}
> TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation
> --
>
> Key: GUACAMOLE-1124
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1124
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
>Affects Versions: 1.1.0, 1.2.0
>Reporter: Tim Worcester
>Priority: Minor
> Attachments: image-2020-07-03-12-31-46-463.png
>
>
> I can't seem to find TEXT_CLIENT_STATUS_UNSTABLE in en.json
> !image-2020-07-03-12-31-46-463.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1124) TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation
[ https://issues.apache.org/jira/browse/GUACAMOLE-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151079#comment-17151079 ] Nick Couchman commented on GUACAMOLE-1124: -- I see it, here: https://github.com/apache/guacamole-client/blob/475d9419cc727b59a0be50903c2c3510565e3488/guacamole/src/main/webapp/translations/en.json#L145 > TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation > -- > > Key: GUACAMOLE-1124 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1124 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.1.0, 1.2.0 >Reporter: Tim Worcester >Priority: Minor > Attachments: image-2020-07-03-12-31-46-463.png > > > I can't seem to find TEXT_CLIENT_STATUS_UNSTABLE in en.json > !image-2020-07-03-12-31-46-463.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1124) TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation
[ https://issues.apache.org/jira/browse/GUACAMOLE-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151080#comment-17151080 ] Nick Couchman commented on GUACAMOLE-1124: -- And, for prior versions: https://github.com/apache/guacamole-client/blob/21ec5640a560f95725c081391d9943d5d0beb88d/guacamole/src/main/webapp/translations/en.json#L145 https://github.com/apache/guacamole-client/blob/ae4361ab70dae4829b08f34a80b08fac885703ba/guacamole/src/main/webapp/translations/en.json#L142 https://github.com/apache/guacamole-client/blob/801a5df9f1d7095c52e594dda1a5276fe8cf6524/guacamole/src/main/webapp/translations/en.json#L141 > TEXT_CLIENT_STATUS_UNSTABLE Missing in English Translation > -- > > Key: GUACAMOLE-1124 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1124 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Affects Versions: 1.1.0, 1.2.0 >Reporter: Tim Worcester >Priority: Minor > Attachments: image-2020-07-03-12-31-46-463.png > > > I can't seem to find TEXT_CLIENT_STATUS_UNSTABLE in en.json > !image-2020-07-03-12-31-46-463.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-1123) Standardize on filtered history query for user and connection management
[ https://issues.apache.org/jira/browse/GUACAMOLE-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1123: Assignee: Nick Couchman > Standardize on filtered history query for user and connection management > > > Key: GUACAMOLE-1123 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1123 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > > When querying connection history, there are several disparate endpoints that > are used to gather that history. Instead of maintaining these various > interfaces, we should standardize on a single connection history endpoint and > update all of the relevant REST calls within the AngularJS application to > reference those calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-531) Docker instructions shall stop using --link to link containers
[ https://issues.apache.org/jira/browse/GUACAMOLE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151109#comment-17151109 ] Nick Couchman commented on GUACAMOLE-531: - [~casperl]: Yes, no one has taken up the challenge, yet :-D. If you're game, you are welcome to work on it! > Docker instructions shall stop using --link to link containers > -- > > Key: GUACAMOLE-531 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-531 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker >Reporter: Gregory Suvalian >Priority: Minor > > As per docker documentation ([https://docs.docker.com/network/links/)] use of > `-link` is deprecated and will eventually be removed in future versions of > docker, it shall be replaced with user defined networks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1110) Size and security improvements for Docker images
[ https://issues.apache.org/jira/browse/GUACAMOLE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1110: - Fix Version/s: 1.3.0 > Size and security improvements for Docker images > > > Key: GUACAMOLE-1110 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1110 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-server >Reporter: Mathias >Priority: Trivial > Labels: Docker, dockerfile > Fix For: 1.3.0 > > > Higher Security: It is best practice to run a daemon as non privileged user. > Health check: Docker can detect if a container is still working. > Docker image size: Not all recommended packages must be installed for the > final image. This small improvement can reduce the size by 200 MB. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1110) Size and security improvements for Docker images
[ https://issues.apache.org/jira/browse/GUACAMOLE-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1110: - Affects Version/s: (was: 1.1.0) > Size and security improvements for Docker images > > > Key: GUACAMOLE-1110 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1110 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-server >Reporter: Mathias >Priority: Trivial > Labels: Docker, dockerfile > > Higher Security: It is best practice to run a daemon as non privileged user. > Health check: Docker can detect if a container is still working. > Docker image size: Not all recommended packages must be installed for the > final image. This small improvement can reduce the size by 200 MB. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1122) Fail in compile of RDP protocol when SSH is unavailable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1122. -- Resolution: Fixed > Fail in compile of RDP protocol when SSH is unavailable > --- > > Key: GUACAMOLE-1122 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1122 > Project: Guacamole > Issue Type: Bug > Components: RDP >Affects Versions: 1.2.0 >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.3.0 > > > As reported on the mailing list [1], when SSH support is disabled RDP will > fail to compile due to a variable scope issue with the settings in the file > redirection portion of RDP. > [1] - > http://mail-archives.apache.org/mod_mbox/guacamole-user/202007.mbox/%3CCALKeL-PHdDQYjSp0MyivmE9dwhv3a02k%2By839oQtDeho8bb6-A%40mail.gmail.com%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-708) Allow database storage of arbitrary attributes for non-database users
[ https://issues.apache.org/jira/browse/GUACAMOLE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151977#comment-17151977 ] Nick Couchman commented on GUACAMOLE-708: - [~p1c0]: Currently no option like that exists. In my experience 2FA/MFA is something you enable at a system level and don't really want specific groups of people to be included/excluded from. However, if you'd like an option to be introduced you should open a new JIRA issue requesting that as an improvement, and, if you are able and so inclined, attempt to implement it and submit a pull request. Beyond that, please avoid asking questions on closed JIRA issues - start with the mailing list and then submit a new JIRA issue if you've found a bug or would like a new feature implemented. > Allow database storage of arbitrary attributes for non-database users > - > > Key: GUACAMOLE-708 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-708 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-jdbc >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > A feature common to other applications that store data in one place and can > authenticate from other sources is to enable automatic creation of user > accounts within the database assuming the user is successfully authenticated > elsewhere. > I propose doing something similar with the Guacamole JDBC extension, or, > depending on how the implementation works out, with the other extensions - a > property that, disabled by default, could be enabled that would allow users > authenticated successfully through other extensions to be automatically > created within the JDBC extension. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1030) LDAP and Database does not allow LDAP only users to create connections
[ https://issues.apache.org/jira/browse/GUACAMOLE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152741#comment-17152741 ] Nick Couchman commented on GUACAMOLE-1030: -- [~Roemer]: Yes, looks like I missed adding that to the Docker startup. I'll create a new JIRA issue for that and we can get that added. For the time being you'll have to find a way to manually add it. Sorry about that. > LDAP and Database does not allow LDAP only users to create connections > -- > > Key: GUACAMOLE-1030 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1030 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Roman Bäriswyl >Priority: Minor > > Following Scenario: > I have LDAP authentication and database enabled. > I have created a group "MyGroup" in the DB and assigned it create > connections/create connection groups rights. > The group "MyGroup" exists in LDAP and "user_a" is inside it. > Now when the "user_a" logs in into guacamole, it correctly seems to have > rights to create groups / connection groups. > Uppon creating a connection or a connection group, guacamole shows > "Unexpected internal error". In the log, I see: > "ERROR: null value in column "entity_id" violates not-null constrait" in a > query that seems to insert permissions into > "guacamole_connection_group_permission". > I suspect the entity_id is the id of the user which does not exist for users > that are only in LDAP. > Does this mean that I manually have to add all users to the DB that should be > able to create connections or connection groups? Wouldn't it be possible for > guacamole to automatically create users (without a password) for LDAP users > in the database? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GUACAMOLE-1128) Add account auto-create options to Docker
Nick Couchman created GUACAMOLE-1128: Summary: Add account auto-create options to Docker Key: GUACAMOLE-1128 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1128 Project: Guacamole Issue Type: Improvement Components: guacamole-auth-jdbc-mysql, guacamole-auth-jdbc-postgresql, guacamole-auth-jdbc-sqlserver Reporter: Nick Couchman GUACAMOLE-708 was successfully implemented as part of the 1.2.0 release, but the variables for the docker script to allow auto-create to be enabled where not added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1119) Unable to query list of objects from LDAP directory
[ https://issues.apache.org/jira/browse/GUACAMOLE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1119. Resolution: Invalid > Unable to query list of objects from LDAP directory > --- > > Key: GUACAMOLE-1119 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1119 > Project: Guacamole > Issue Type: Bug > Components: guacamole, guacamole-auth-ldap >Affects Versions: 1.2.0 > Environment: guacamole 1.2.0, guacd 1.2.0 running in a docker > container on Ubuntu Linux talking to Azure ADDS for secure LDAP >Reporter: Ed Withers >Priority: Minor > > We run guacamole in a docker container on an Ubuntu Linux machine. We use > Postgres for the database and secure LDAP for authentication connecting to > Azure Active Directory Domain Services. We have been running this > configuration with version 1.1.0 of guacamole and guac_d since at least last > August. The update to 1.2.0 broke that integration. > Symptom: User attempts to log in, after entering username and password, there > is a long delay and then the error "Unable to query list of objects from LDAP > directory" appears at the top of the screen and the user remains at the login > page. > docker logs show that the user successfully authenticated. > tcpdump shows traffic flowing between the guacamole container and the LDAP > server. > Reverting back to version 1.1.0 "solved" the problem. > We suspect that the new LDAP configuration options changed a default behavior > to something that is incompatible with the Azure ADDS schema. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1126) Implement Maximum auto-reconnect attempts
[ https://issues.apache.org/jira/browse/GUACAMOLE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152135#comment-17152135 ] Nick Couchman commented on GUACAMOLE-1126: -- [~erodriguez19]: I think we've discussed this in the past as something we'd like to implement; however, I would suggest that it be a configurable setting rather than a set number of tries, and that it default to continuous retries (the current behavior) unless otherwise configured. This should likely be a Connection Attribute (vs. Parameter), similar to the load balancing stuff. I also think it's probably worth taking the time to work through implementing the counter (1/4, 2/4, etc.) - we can help you through that. Feel free to submit the pull request (maybe put it in draft mode) and we can work through it. > Implement Maximum auto-reconnect attempts > - > > Key: GUACAMOLE-1126 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1126 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Reporter: Edgardo Rodriguez >Priority: Minor > > Using guacamole for 60+ users I've realized that sometimes, RDP hosts "go > away" because of hardware issues, dns issues, etc and users might not be > aware of it. > For example, they leave their computer with the browser open with session > established and going on... When this happens, Guacamole tries to > auto-reconnect every 15 seconds without any limitation (some times > indefinitely) and also, SESSION TIMER is renewed because of fake? user > activity. > I've implemented a counter which allows automatic reconnection attempts for > up to 4 tries. When tried 4 times, countdown timer is not further applied and > so user is left with manual Reconnect dialog prompt as usual. > I `ve not implemented a visual indication like 1/4 2/4,etc because it > involves transalations and other "more complex" stuff. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1125) Ctrl+Alt+End(Supr) only working once
[ https://issues.apache.org/jira/browse/GUACAMOLE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-1125. -- Resolution: Fixed [~erodriguez19]: Thanks for the fix! > Ctrl+Alt+End(Supr) only working once > > > Key: GUACAMOLE-1125 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1125 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Reporter: Edgardo Rodriguez >Priority: Minor > > Starting with guacamole-version 1.2.0 I observed that my shorcut keys ceased > to work correctly. > I thought it was related to GUACAMOLE-518 but in fact that just made things > work "better"!! > Tracked down the issue to > [clientController.js|https://github.com/apache/guacamole-client/blob/475d9419cc727b59a0be50903c2c3510565e3488/guacamole/src/main/webapp/app/client/controllers/clientController.js#L678] > where I saw that "substituteKeysPressed[keysym]" was deleted prior to > "guacSyntheticKeyup" being submitted. > I am running a few more tests and will prepare a pull request. > Steps to reproduce are as follow: > 1- Have guacamole-client/server version 1.2.0 > 2- Press Ctrl+Alt+End combo and see "Windows Ctrl+Alt+Supr" behaviour. > 3- Repeat again previous combo and from now on nothing happens. > 4- Press "Supr" key once alone and then repeat step 2 combo and it works once > again! > > Solution seems to first send "guacSyntheticKeyup" and then actually delete > "substituteKeysPressed[keysym]" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1125) Ctrl+Alt+End(Supr) only working once
[ https://issues.apache.org/jira/browse/GUACAMOLE-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1125: - Fix Version/s: 1.3.0 > Ctrl+Alt+End(Supr) only working once > > > Key: GUACAMOLE-1125 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1125 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client >Reporter: Edgardo Rodriguez >Priority: Minor > Fix For: 1.3.0 > > > Starting with guacamole-version 1.2.0 I observed that my shorcut keys ceased > to work correctly. > I thought it was related to GUACAMOLE-518 but in fact that just made things > work "better"!! > Tracked down the issue to > [clientController.js|https://github.com/apache/guacamole-client/blob/475d9419cc727b59a0be50903c2c3510565e3488/guacamole/src/main/webapp/app/client/controllers/clientController.js#L678] > where I saw that "substituteKeysPressed[keysym]" was deleted prior to > "guacSyntheticKeyup" being submitted. > I am running a few more tests and will prepare a pull request. > Steps to reproduce are as follow: > 1- Have guacamole-client/server version 1.2.0 > 2- Press Ctrl+Alt+End combo and see "Windows Ctrl+Alt+Supr" behaviour. > 3- Repeat again previous combo and from now on nothing happens. > 4- Press "Supr" key once alone and then repeat step 2 combo and it works once > again! > > Solution seems to first send "guacSyntheticKeyup" and then actually delete > "substituteKeysPressed[keysym]" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1135) MySQL SSL - Trust Store Paths Expecting URI
[
https://issues.apache.org/jira/browse/GUACAMOLE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1135:
-
Component/s: guacamole-auth-jdbc-mysql
> MySQL SSL - Trust Store Paths Expecting URI
> ---
>
> Key: GUACAMOLE-1135
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1135
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-auth-jdbc-mysql
>Affects Versions: 1.2.0
>Reporter: Richard Grime
>Priority: Minor
>
> I'm seeing:
> {code:java}
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> /path/to/truststore.jks does not appear to be a valid URL.
> {code}
> It looks like the driver is expecting a URI, rather than plain file path?
> [MySQLAuthenticationProviderModule.java|https://github.com/apache/guacamole-client/pull/492/commits/721010cc14bd565a31faff14d9a020973128565c#diff-e8178383030ac1b242f3c02d548c882a]
> currently reads:
> {code:java}
> driverProperties.setProperty("trustCertificateKeyStoreUrl",
> trustStore.getAbsolutePath());
> {code}
> Is there a missing .toUri() ? (And in clientCertificateKeyStoreUrl) - or is
> there any example of how to configure this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1135) MySQL SSL - Trust Store Paths Expecting URI
[
https://issues.apache.org/jira/browse/GUACAMOLE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157464#comment-17157464
]
Nick Couchman commented on GUACAMOLE-1135:
--
[~rsg98]: Okay, we'll try to get that fixed up for the next release.
> MySQL SSL - Trust Store Paths Expecting URI
> ---
>
> Key: GUACAMOLE-1135
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1135
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-auth-jdbc-mysql
>Affects Versions: 1.2.0
>Reporter: Richard Grime
>Priority: Minor
>
> I'm seeing:
> {code:java}
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> /path/to/truststore.jks does not appear to be a valid URL.
> {code}
> It looks like the driver is expecting a URI, rather than plain file path?
> [MySQLAuthenticationProviderModule.java|https://github.com/apache/guacamole-client/pull/492/commits/721010cc14bd565a31faff14d9a020973128565c#diff-e8178383030ac1b242f3c02d548c882a]
> currently reads:
> {code:java}
> driverProperties.setProperty("trustCertificateKeyStoreUrl",
> trustStore.getAbsolutePath());
> {code}
> Is there a missing .toUri() ? (And in clientCertificateKeyStoreUrl) - or is
> there any example of how to configure this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1135) MySQL SSL - Trust Store Paths Expecting URI
[
https://issues.apache.org/jira/browse/GUACAMOLE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1135:
-
Priority: Minor (was: Major)
> MySQL SSL - Trust Store Paths Expecting URI
> ---
>
> Key: GUACAMOLE-1135
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1135
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-mysql
>Affects Versions: 1.2.0
>Reporter: Richard Grime
>Priority: Minor
>
> I'm seeing:
> {code:java}
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> /path/to/truststore.jks does not appear to be a valid URL.
> {code}
> It looks like the driver is expecting a URI, rather than plain file path?
> [MySQLAuthenticationProviderModule.java|https://github.com/apache/guacamole-client/pull/492/commits/721010cc14bd565a31faff14d9a020973128565c#diff-e8178383030ac1b242f3c02d548c882a]
> currently reads:
> {code:java}
> driverProperties.setProperty("trustCertificateKeyStoreUrl",
> trustStore.getAbsolutePath());
> {code}
> Is there a missing .toUri() ? (And in clientCertificateKeyStoreUrl) - or is
> there any example of how to configure this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1135) MySQL SSL - Trust Store Paths Expecting URI
[
https://issues.apache.org/jira/browse/GUACAMOLE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1135:
-
Component/s: (was: guacamole-auth-jdbc-mysql)
Documentation
> MySQL SSL - Trust Store Paths Expecting URI
> ---
>
> Key: GUACAMOLE-1135
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1135
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 1.2.0
>Reporter: Richard Grime
>Priority: Minor
>
> I'm seeing:
> {code:java}
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> /path/to/truststore.jks does not appear to be a valid URL.
> {code}
> It looks like the driver is expecting a URI, rather than plain file path?
> [MySQLAuthenticationProviderModule.java|https://github.com/apache/guacamole-client/pull/492/commits/721010cc14bd565a31faff14d9a020973128565c#diff-e8178383030ac1b242f3c02d548c882a]
> currently reads:
> {code:java}
> driverProperties.setProperty("trustCertificateKeyStoreUrl",
> trustStore.getAbsolutePath());
> {code}
> Is there a missing .toUri() ? (And in clientCertificateKeyStoreUrl) - or is
> there any example of how to configure this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1135) MySQL SSL - Trust Store Paths Expecting URI
[
https://issues.apache.org/jira/browse/GUACAMOLE-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157455#comment-17157455
]
Nick Couchman commented on GUACAMOLE-1135:
--
The format would be:
file:///path/to/trust/store
> MySQL SSL - Trust Store Paths Expecting URI
> ---
>
> Key: GUACAMOLE-1135
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1135
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-mysql
>Affects Versions: 1.2.0
>Reporter: Richard Grime
>Priority: Major
>
> I'm seeing:
> {code:java}
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> /path/to/truststore.jks does not appear to be a valid URL.
> {code}
> It looks like the driver is expecting a URI, rather than plain file path?
> [MySQLAuthenticationProviderModule.java|https://github.com/apache/guacamole-client/pull/492/commits/721010cc14bd565a31faff14d9a020973128565c#diff-e8178383030ac1b242f3c02d548c882a]
> currently reads:
> {code:java}
> driverProperties.setProperty("trustCertificateKeyStoreUrl",
> trustStore.getAbsolutePath());
> {code}
> Is there a missing .toUri() ? (And in clientCertificateKeyStoreUrl) - or is
> there any example of how to configure this?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1137) User can not change the own password
[ https://issues.apache.org/jira/browse/GUACAMOLE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1137: - Priority: Minor (was: Critical) > User can not change the own password > > > Key: GUACAMOLE-1137 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1137 > Project: Guacamole > Issue Type: Bug >Reporter: Stefan >Priority: Minor > > We noticed some strange behavior when the user wants to change its password. > When there is a "@” sign in the username and he not an administrator the > password change is not possible. (tomcat-server response with 404). > As admin has an "@" in the username is no problem. > Also, when the non-admin-user has no "@" in the username the password change > is working. > We started search but up to now we have no idea where the issue happens… > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1132) add Web connection type to remote server
[ https://issues.apache.org/jira/browse/GUACAMOLE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158473#comment-17158473 ] Nick Couchman commented on GUACAMOLE-1132: -- [~slhotellier]: I understand your desire to have this feature, but it continues to be outside the scope of the Guacamole project. Someone in the community might have an extension for it or some way to accomplish this, but as a project we are trying to avoid scope and feature creep in introducing things like this that are unrelated to the overall goal of producing a remote desktop client. > add Web connection type to remote server > > > Key: GUACAMOLE-1132 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1132 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Affects Versions: 1.2.0 > Environment: CENTOS 8.2 >Reporter: Stephane L'Hotellier >Priority: Major > > Hello > In order to replace our homemaid connection manager, we plan to switch to > Guacamole. > the only lack that we have noted for the moment is the possibility of > managing web connections (http and https). > Is it possible in one of the next versions, to embed a Web browser? > Or at least post web links on the home page? > Best regards -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1111) Guacamole gives error after updating Tomcat
[ https://issues.apache.org/jira/browse/GUACAMOLE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-. Resolution: Invalid > Guacamole gives error after updating Tomcat > --- > > Key: GUACAMOLE- > URL: https://issues.apache.org/jira/browse/GUACAMOLE- > Project: Guacamole > Issue Type: Bug > Components: guacamole, guacd >Affects Versions: 1.1.0 >Reporter: Michael Vasile >Priority: Minor > Labels: error, tomcat > Attachments: image-2020-06-25-12-05-14-110.png > > > I have Guacamole installed on a RHEL 7 server. After installing an update to > Tomcat, Guacamole has broken and I get this error when trying to access it. > !image-2020-06-25-12-05-14-110.png! > I tried checking catalina.out and did not see any errors in the logs. Not > sure if there's anywhere else that would need to be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1096) Typeable keys on Mac involving Alt do not have intended effect
[ https://issues.apache.org/jira/browse/GUACAMOLE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151408#comment-17151408 ] Nick Couchman commented on GUACAMOLE-1096: -- [~WCityMike]: Version 1.2.0 underwent some pretty significant updates with respect to modifier keys. Can you re-test with 1.2.0 and see what happens? > Typeable keys on Mac involving Alt do not have intended effect > -- > > Key: GUACAMOLE-1096 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1096 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.1.0 >Reporter: Mike Harris >Priority: Major > > Seeking to migrate [GUAC-1519|https://jira.glyptodon.com/browse/GUAC-1519] to > current bug tracker. As the original reporter suggests, there are plenty of > instances within a Windows OS (and others) where an Alt-and-key combination > is desirable to move quickly on a task. > As Michael Jumper noted in that thread noted: "I think the root cause of your > issue is in the difference in meaning for 'Alt' in a Mac vs. Windows ... We > need to find some way to recognize when Alt is being held strictly for the > sake of typing, as Ctrl+Alt may be held under Windows, and release it for the > same reasons. The big question is whether that is actually possible to > achieve without breaking keyboard in other cases." > Forgive me if I've done anything wrong in the filing of this bug; first time > I've done it on this system. Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1067) Update guacd Docker image with FreeRDP 2.1
[ https://issues.apache.org/jira/browse/GUACAMOLE-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1067. Resolution: Invalid Current images should be built against this version, already. > Update guacd Docker image with FreeRDP 2.1 > -- > > Key: GUACAMOLE-1067 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1067 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker, guacamole-server >Reporter: Marcos >Priority: Major > > FreeRDP has released version 2.1 fixing several vulnerabilities in 2.0. We > should insure that the Guacamole Server code compiles against it, and bring > the Docker image up-to-date with this version, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1108) Memory leak on RDP sessions
[ https://issues.apache.org/jira/browse/GUACAMOLE-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1108. Resolution: Invalid [~matteustace]: Please test, again, with version 1.2.0 and see if you're still seeing the issue. If so, feel free to re-open this, and if you can provide valgrind information, that would be helpful. > Memory leak on RDP sessions > --- > > Key: GUACAMOLE-1108 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1108 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Matt Eustace >Priority: Major > > I am experiencing a severe memory leak in the guacd process. > Generally speaking it slowly uses up more and more memory, but if a user is > streaming video it uses hundreds of a meg per second until there's no memory > or swap left, then the server falls over and kicks everyone out, they > reconnect, and we start all over again. > This seems to be happening several times a day. > > This is Guacamole 1.1.0 running on Ubuntu Server 18.04 LTS, using RDP. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1030) LDAP and Database does not allow LDAP only users to create connections
[ https://issues.apache.org/jira/browse/GUACAMOLE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151423#comment-17151423 ] Nick Couchman commented on GUACAMOLE-1030: -- [~Roemer]: With the implementation of GUACAMOLE-708, you should be able to set the -auto-create-accounts option in your guacamole.properties file and users will be automatically created, thus allowing them to create connections. > LDAP and Database does not allow LDAP only users to create connections > -- > > Key: GUACAMOLE-1030 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1030 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Roman Bäriswyl >Priority: Minor > > Following Scenario: > I have LDAP authentication and database enabled. > I have created a group "MyGroup" in the DB and assigned it create > connections/create connection groups rights. > The group "MyGroup" exists in LDAP and "user_a" is inside it. > Now when the "user_a" logs in into guacamole, it correctly seems to have > rights to create groups / connection groups. > Uppon creating a connection or a connection group, guacamole shows > "Unexpected internal error". In the log, I see: > "ERROR: null value in column "entity_id" violates not-null constrait" in a > query that seems to insert permissions into > "guacamole_connection_group_permission". > I suspect the entity_id is the id of the user which does not exist for users > that are only in LDAP. > Does this mean that I manually have to add all users to the DB that should be > able to create connections or connection groups? Wouldn't it be possible for > guacamole to automatically create users (without a password) for LDAP users > in the database? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1021) Top level organizational level of connection group repeated when user is in two groups that contain different hosts
[ https://issues.apache.org/jira/browse/GUACAMOLE-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151426#comment-17151426 ] Nick Couchman commented on GUACAMOLE-1021: -- [~kangaroo22]: Can you test with version 1.2.0 and see if the behavior still exists? I know Mike fixed a couple of issues related to display of Organizational Groups, and I'm wondering if that has taken care of things? > Top level organizational level of connection group repeated when user is in > two groups that contain different hosts > --- > > Key: GUACAMOLE-1021 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1021 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Reporter: Jason Keltz >Priority: Minor > > A user is in two groups that refer to the same organizational level of the > connection group, and different hosts underneath. The system displays the > title of the organization level twice - one of them is greyed out, and the > other can be used. When the user has access to the same organizational level > in both groups, only one group should be displayed. > One connection group top-level is created called "Connect with SSH" which > contains 4 hosts. > Group1 contains the top-level "Connect with SSH" and two of the hosts. > Connect with SSH > * Host 1 > * Host 2 > Group 2 contains the top-level "Connect with SSH" and the other two hosts. > * Host 1 > * Host 2 > A user in both groups sees: > + Connect with SSH (greyed out, not selectable) > + Connect with SSH > * Host 1 > * Host 2 > * Host 3 > * Host 4 > Expected Behaviour: User sees "Connect with SSH" only one time. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1030) LDAP and Database does not allow LDAP only users to create connections
[ https://issues.apache.org/jira/browse/GUACAMOLE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1030. Resolution: Fixed > LDAP and Database does not allow LDAP only users to create connections > -- > > Key: GUACAMOLE-1030 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1030 > Project: Guacamole > Issue Type: Bug >Affects Versions: 1.1.0 >Reporter: Roman Bäriswyl >Priority: Minor > > Following Scenario: > I have LDAP authentication and database enabled. > I have created a group "MyGroup" in the DB and assigned it create > connections/create connection groups rights. > The group "MyGroup" exists in LDAP and "user_a" is inside it. > Now when the "user_a" logs in into guacamole, it correctly seems to have > rights to create groups / connection groups. > Uppon creating a connection or a connection group, guacamole shows > "Unexpected internal error". In the log, I see: > "ERROR: null value in column "entity_id" violates not-null constrait" in a > query that seems to insert permissions into > "guacamole_connection_group_permission". > I suspect the entity_id is the id of the user which does not exist for users > that are only in LDAP. > Does this mean that I manually have to add all users to the DB that should be > able to create connections or connection groups? Wouldn't it be possible for > guacamole to automatically create users (without a password) for LDAP users > in the database? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-801) Capslock / Shift key passthrough is strange over dual RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151425#comment-17151425 ] Nick Couchman commented on GUACAMOLE-801: - [~Why4ArtThou]: Can you re-test with version 1.2.0 and see if the issue is resolved, there? The modified key behavior underwent significant changes in the 1.2.0 release. > Capslock / Shift key passthrough is strange over dual RDP > - > > Key: GUACAMOLE-801 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-801 > Project: Guacamole > Issue Type: Bug >Reporter: Robert McGunsterson >Priority: Minor > Labels: input > > I am using guac to get home. > From the guac UI, I open a full screen RDP to my desktop. > From my home desktop, I am then opening /another/ RDP session within my > existing RDP session. > > When I do this, typing out stuff comes out very strange in relation to the > shift key and this seems a consistent fault, specifically causing issues with > passwords utilising the shift key. > > See text below > > thIs is mE TypIng With thE CApS locK ON, iN AN RdP sESsIon > ThiS iS Me HOLdiNg dowN thE riGHT shIFT kEY > THIS IS ME HOLDING DOWN THE LEFT SHIFT KEY > > I do not know the cause of this, it's a pretty obscure problem, but it's > specific to guac. It's like the way guac forwards a shift key is not > persistent? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1093) Guacamole changes Timezone when logging in
[ https://issues.apache.org/jira/browse/GUACAMOLE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1093. Resolution: Invalid > Guacamole changes Timezone when logging in > -- > > Key: GUACAMOLE-1093 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1093 > Project: Guacamole > Issue Type: Bug >Reporter: Riano de Souza >Priority: Minor > > So as the title says Guacamole changes my timezone from utc +2 to UTC when > logging in. > I am running it in a docker container and have checked all dates and times on > all the different containers all is on the correct timezone. > > I even tried forcing the timezone in connection settings but it just keeps > changing it back to UTC does not matter what i change. > > What else can i check in terms of timezone settings? any environmental > variables to check and test with? > > Your help will be appreciated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-862) ctrl+c invalid when caps lock turn on in rdp
[ https://issues.apache.org/jira/browse/GUACAMOLE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151428#comment-17151428 ] Nick Couchman commented on GUACAMOLE-862: - [~vicent.wu]: Can you re-test with 1.2.0 and see if this issue still exists? There was a significant update in 1.2.0 for modifier keys that may resolve this issue. > ctrl+c invalid when caps lock turn on in rdp > > > Key: GUACAMOLE-862 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-862 > Project: Guacamole > Issue Type: Bug > Components: guacamole >Affects Versions: 1.0.0 >Reporter: vicent.wu >Priority: Minor > Labels: windows > > Connect rdp windows server when capslock is turned on > Ctrl+c character can't be ctrl+v paste > Right copy can be ctrl+v paste -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-760) add timezone info using DB Connection string
[ https://issues.apache.org/jira/browse/GUACAMOLE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-760: Fix Version/s: 1.3.0 > add timezone info using DB Connection string > > > Key: GUACAMOLE-760 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-760 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-client >Affects Versions: 1.0.0 >Reporter: Not Speedy >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.3.0 > > > a recent update to with mariadb or its driver prevented guacamole client from > loading. > Cause: java.sql.SQLException: The server time zone value 'CDT' is > unrecognized or represents more than one time zone. You must configure either > the server or JDBC driver (via the serverTimezone configuration property). > loading the timezone table and setting it globally on the mariadb resolved > this, however it might be beneficial to add a system property that will set > within the connection string. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-985) Terminal clipboard should convert newline characters as needed
[ https://issues.apache.org/jira/browse/GUACAMOLE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-985. --- Resolution: Duplicate > Terminal clipboard should convert newline characters as needed > -- > > Key: GUACAMOLE-985 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-985 > Project: Guacamole > Issue Type: Bug > Components: Kubernetes, SSH, Telnet, Terminal >Affects Versions: 1.1.0 >Reporter: Ignacio Turégano >Priority: Minor > Attachments: Problem.png, Workaround.png > > > Hi everyone, > We have found an issue with the clipboard when using it from windows (CR LF) > and destination Linux (LF). Guacamole inserts a new line between lines. If we > copy the text in notepad++ and transform it to Unix style then the copy & > paste works like a charm. > Thank you!!! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-349) RDP keymap translation unnecessarily presses SHIFT_L when SHIFT_R is held
[ https://issues.apache.org/jira/browse/GUACAMOLE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151438#comment-17151438 ] Nick Couchman commented on GUACAMOLE-349: - [~sebastian.ohmsen]: Are you able to re-test in version 1.2.0? There were significant keymap updates that may have resolved this... > RDP keymap translation unnecessarily presses SHIFT_L when SHIFT_R is held > - > > Key: GUACAMOLE-349 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-349 > Project: Guacamole > Issue Type: Bug > Components: RDP >Reporter: Sebastian Ohmsen >Priority: Minor > > We've come across a bug that is corrupting the user input for guacamole > sessions over rdp. The problem only occurs when you open a RDP session inside > the RDP session established by guacamole. Our use case is that we connect to > a Hyper-V server and would open the console of a VM running on it. You can > very well test that too with connecting to any RDP server from the connection > established by guacamole. > We've tested this extensively and we can observe the following: Whenever you > press a key combination that produces another result by adding a modifier > key, like "SHIFT_R + ."(dot) which should lead to an ">" sign, it's only a > matter of time when this is mapped to a "."(dot) sign. This does not only > occur when you hold both keys down, it also occurs occasionally when you > press it the first time. This makes entering passwords super hard and seems > to be a bug. > We've traced it down to the corresponding C code and think the problem is > here: > https://github.com/apache/incubator-guacamole-server/blob/master/src/protocols/rdp/keyboard.c#L261 > In some cases of extra mapped keys, for example in the above case, it's > sending more keys than expected. We can see that “SHIFT_L + .” results in > following keysym updates: > > * 0xFFE1 (SHIFT_L) pressed > * 0x003E (>) pressed > * 0x003E (>) released > * 0xFFE1 (SHIFT_L) released > and works perfectly fine. In contrast “SHIFT_R + .” results in following > events: > * 0xFFE2 (SHIFT_R) pressed > * 0xFFE1 (SHIFT_L) pressed > * 0x003E (>) pressed > * 0xFFE1 (SHIFT_L) released > * 0xFFE1 (SHIFT_L) pressed > * 0x003E (>) released > * 0xFFE1 (SHIFT_L) released > * 0xFFE2 (SHIFT_R) released > which leads to the described behavior above. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-1107) "allowed-languages" property incorrectly documented as "available-languages"
[
https://issues.apache.org/jira/browse/GUACAMOLE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reassigned GUACAMOLE-1107:
Assignee: Nick Couchman
> "allowed-languages" property incorrectly documented as "available-languages"
>
>
> Key: GUACAMOLE-1107
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1107
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation
>Reporter: Ji Shoukai
>Assignee: Nick Couchman
>Priority: Trivial
> Fix For: 1.3.0
>
>
> The Guacamole web application allows the display languages presented to the
> user to be limited through specifying [the {{allowed-languages}}
> property|https://github.com/apache/guacamole-client/blob/577eca819f67d17fab71745519421dca1eb57b01/guacamole/src/main/java/org/apache/guacamole/extension/LanguageResourceService.java#L77-L88].
> This property is incorrectly documented in the manual as
> [{{available-languages}}|http://guacamole.apache.org/doc/1.1.0/gug/configuring-guacamole.html#initial-setup].
> The documentation should be corrected to note the correct property name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-560) Include "state" parameter in OpenID Connect authorization request
[
https://issues.apache.org/jira/browse/GUACAMOLE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-560:
Affects Version/s: (was: 0.9.14)
> Include "state" parameter in OpenID Connect authorization request
> -
>
> Key: GUACAMOLE-560
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-560
> Project: Guacamole
> Issue Type: Wish
> Components: guacamole-auth-openid
>Reporter: Dave Smith
>Priority: Trivial
>
> {quote}i've tried to get this setup. Unfortunately it seems Okta insist (even
> with Single Page App (SPA)) to have state field in the POST even if (when
> using SPA) it's not actually used. The guacamole client just goes in a
> redirect loop with error in URL visible of "invalid state".
>
> With SPA the state parameter can even be some random letters, but must be
> there. Using OIDCDebugger.com gleans this:{quote}
> {quote}
> error=invalid_request
> error_description=The authentication request has an invalid state
> parameter.
>
> yet by adding a bunch of x's to the state parameter..
>
> i get a much more positive response:
> state=x
> id_token=eyJraWQiOiI0NlpNbjlZZG5HQ1AxMGhDUWs5VWtvc2ljUmltTURJRDBBbVh1dWhHUUhrIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiIwMHUxMDAxNnVwUzhFaENuMjJwNyIsInZlciI6MSwiaXNzIjoiaHR0cHM6Ly9hdG9zbXBjYXdzLm9rdGEuY29tIiwiYXVkIjoiMG9hMTIzZG8weXNibFN4dUoycDciLCJpYXQiOjE1MjQ3NTQwOTUsImV4cCI6MTUyNDc1NzY5NSwianRpIjoiSUQuRmZGYzFpZlA2VG
>
> I'd kindly ask that state could be added as an optional parameter to the guac
> properties file.{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-560) Include "state" parameter in OpenID Connect authorization request
[
https://issues.apache.org/jira/browse/GUACAMOLE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reassigned GUACAMOLE-560:
---
Assignee: Nick Couchman
> Include "state" parameter in OpenID Connect authorization request
> -
>
> Key: GUACAMOLE-560
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-560
> Project: Guacamole
> Issue Type: Wish
> Components: guacamole-auth-openid
>Reporter: Dave Smith
>Assignee: Nick Couchman
>Priority: Trivial
>
> {quote}i've tried to get this setup. Unfortunately it seems Okta insist (even
> with Single Page App (SPA)) to have state field in the POST even if (when
> using SPA) it's not actually used. The guacamole client just goes in a
> redirect loop with error in URL visible of "invalid state".
>
> With SPA the state parameter can even be some random letters, but must be
> there. Using OIDCDebugger.com gleans this:{quote}
> {quote}
> error=invalid_request
> error_description=The authentication request has an invalid state
> parameter.
>
> yet by adding a bunch of x's to the state parameter..
>
> i get a much more positive response:
> state=x
> id_token=eyJraWQiOiI0NlpNbjlZZG5HQ1AxMGhDUWs5VWtvc2ljUmltTURJRDBBbVh1dWhHUUhrIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiIwMHUxMDAxNnVwUzhFaENuMjJwNyIsInZlciI6MSwiaXNzIjoiaHR0cHM6Ly9hdG9zbXBjYXdzLm9rdGEuY29tIiwiYXVkIjoiMG9hMTIzZG8weXNibFN4dUoycDciLCJpYXQiOjE1MjQ3NTQwOTUsImV4cCI6MTUyNDc1NzY5NSwianRpIjoiSUQuRmZGYzFpZlA2VG
>
> I'd kindly ask that state could be added as an optional parameter to the guac
> properties file.{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1107) "allowed-languages" property incorrectly documented as "available-languages"
[
https://issues.apache.org/jira/browse/GUACAMOLE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1107:
-
Fix Version/s: 1.3.0
> "allowed-languages" property incorrectly documented as "available-languages"
>
>
> Key: GUACAMOLE-1107
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1107
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation
>Reporter: Ji Shoukai
>Priority: Trivial
> Fix For: 1.3.0
>
>
> The Guacamole web application allows the display languages presented to the
> user to be limited through specifying [the {{allowed-languages}}
> property|https://github.com/apache/guacamole-client/blob/577eca819f67d17fab71745519421dca1eb57b01/guacamole/src/main/java/org/apache/guacamole/extension/LanguageResourceService.java#L77-L88].
> This property is incorrectly documented in the manual as
> [{{available-languages}}|http://guacamole.apache.org/doc/1.1.0/gug/configuring-guacamole.html#initial-setup].
> The documentation should be corrected to note the correct property name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1051) Bloq Mayus not working with RDP
[
https://issues.apache.org/jira/browse/GUACAMOLE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151442#comment-17151442
]
Nick Couchman commented on GUACAMOLE-1051:
--
[~erodriguez19]: Can you re-test with the 1.2.0 release and see if it works?
Some significant changes were made in May and June for the 1.2.0 release that
may correct this.
> Bloq Mayus not working with RDP
> ---
>
> Key: GUACAMOLE-1051
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1051
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
>Affects Versions: 1.1.0, 1.2.0
>Reporter: Edgardo Rodriguez
>Priority: Trivial
>
> Hi,
> Building and testing guacamole *staging/1.2.0* from scratch, I found that
> during a RDP session there is an *issue with Bloq Mayus key*.
> Pressing it does nothing (going elsewhere like another tab/webpage, shows
> that mayus key is working).
> I am unsure if this is a specific restriction due the nature of key being
> translated or a bug.
> On the other hand, in a SSH session this is working OK (as desired).
> Pressing Shift+\{Key} does it job ok, as an alternative.
> Also, enabling *Input Method -> Text Input* also restores the intended
> behaviour.
> Keyboard Layout setting for connection profile was tried empty (as default),
> latinamerican (mine), and also spanish without any evident impact.
> *Another important fact:* If before logging-in/connecting to an RDP profile
> you have Bloq Mayus key toggled, everything inside the client will be written
> in upper-case. Also, it's impossible to disable it.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1107) "allowed-languages" property incorrectly documented as "available-languages"
[
https://issues.apache.org/jira/browse/GUACAMOLE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-1107.
--
Resolution: Fixed
> "allowed-languages" property incorrectly documented as "available-languages"
>
>
> Key: GUACAMOLE-1107
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1107
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation
>Reporter: Ji Shoukai
>Assignee: Nick Couchman
>Priority: Trivial
> Fix For: 1.3.0
>
>
> The Guacamole web application allows the display languages presented to the
> user to be limited through specifying [the {{allowed-languages}}
> property|https://github.com/apache/guacamole-client/blob/577eca819f67d17fab71745519421dca1eb57b01/guacamole/src/main/java/org/apache/guacamole/extension/LanguageResourceService.java#L77-L88].
> This property is incorrectly documented in the manual as
> [{{available-languages}}|http://guacamole.apache.org/doc/1.1.0/gug/configuring-guacamole.html#initial-setup].
> The documentation should be corrected to note the correct property name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-877) Add support for Okta MFA
[ https://issues.apache.org/jira/browse/GUACAMOLE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-877. --- Resolution: Duplicate > Add support for Okta MFA > > > Key: GUACAMOLE-877 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-877 > Project: Guacamole > Issue Type: New Feature > Components: guacamole >Reporter: Triet Le >Priority: Minor > Labels: features > > My company has been using Guacamole as our Remote Access solutions the past > few years and it has been very reliable. We would like to strengthen our > security posture by adding a second-factor authentication to our Guacamole > stack. I am looking to develop and integrate Okta as another Guacamole auth > extension. > Thinking this extension would behave very similar to the Duo auth extension. > The authentication steps should follow: > 1. User login Guacamole as usual. > 2. Guacamole attempts to authenticate the user with the first authenticator > (LDAP, MySQL or ...) > 3. Once the first authentication attempt is succeeded, Okta auth extension > rejects the authentication attempt and starts asking for the second-factor > authentication. > 4. Presents the Okta MFA flow and have them navigate through it (enrollment, > activation, authentication) > 5. Once the user has successfully satisfied the MFA challenge, Guacamole > receives a signed response. > 6. Okta auth extension validates the response. If valid, allow the user to > proceed, otherwise, reject. > I believe this extension would add more value to the product. Please let me > know if I am on the right thinking track. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-538) Add the ability to specify separate permissions for "History" and "Active sessions" tabs
[ https://issues.apache.org/jira/browse/GUACAMOLE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-538: --- Assignee: Nick Couchman > Add the ability to specify separate permissions for "History" and "Active > sessions" tabs > > > Key: GUACAMOLE-538 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-538 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Fabian Rodriguez >Assignee: Nick Couchman >Priority: Minor > > In Settings > Users > $USER > Permissions, I'd like to be able to set two > extra permissions: > * access sessions History tab > * access Active Sessions tab. > This would help when it's required to provide a manager access to history and > active sessions, while avoiding giving them full admin rights (change/add > users/connections). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1132) add Web connection type to remote server
[ https://issues.apache.org/jira/browse/GUACAMOLE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1132. Resolution: Won't Do [~slhotellier]: As mentioned in the thread on the mailing list, from the project perspective, we're trying to keep Guacamole focused on remote desktop connections and avoid features that take the project in other directions. It may be possible to implement this functionality in an extension - I think others have done that in the past - but as a feature of Guacamole it isn't something we want to add to the project. > add Web connection type to remote server > > > Key: GUACAMOLE-1132 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1132 > Project: Guacamole > Issue Type: Wish > Components: guacamole >Affects Versions: 1.2.0 > Environment: CENTOS 8.2 >Reporter: Stephane L'Hotellier >Priority: Major > > Hello > In order to replace our homemaid connection manager, we plan to switch to > Guacamole. > the only lack that we have noted for the moment is the possibility of > managing web connections (http and https). > Is it possible in one of the next versions, to embed a Web browser? > Or at least post web links on the home page? > Best regards -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1119) Unable to query list of objects from LDAP directory
[ https://issues.apache.org/jira/browse/GUACAMOLE-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149701#comment-17149701 ] Nick Couchman commented on GUACAMOLE-1119: -- [~ewithers]: There were not very many LDAP changes between 1.1.0 and 1.2.0. The only two changes involve allowing group membership to happen with posixGroups, and fixing an issue with schema updates. I suggest that you: 1) Gather more detailed logs from Tomcat on the cause of the failure. 2) Start the conversation on the u...@guacamole.apache.org mailing list: http://guacamole.apache.org/support/ > Unable to query list of objects from LDAP directory > --- > > Key: GUACAMOLE-1119 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1119 > Project: Guacamole > Issue Type: Bug > Components: guacamole, guacamole-auth-ldap >Affects Versions: 1.2.0 > Environment: guacamole 1.2.0, guacd 1.2.0 running in a docker > container on Ubuntu Linux talking to Azure ADDS for secure LDAP >Reporter: Ed Withers >Priority: Minor > > We run guacamole in a docker container on an Ubuntu Linux machine. We use > Postgres for the database and secure LDAP for authentication connecting to > Azure Active Directory Domain Services. We have been running this > configuration with version 1.1.0 of guacamole and guac_d since at least last > August. The update to 1.2.0 broke that integration. > Symptom: User attempts to log in, after entering username and password, there > is a long delay and then the error "Unable to query list of objects from LDAP > directory" appears at the top of the screen and the user remains at the login > page. > docker logs show that the user successfully authenticated. > tcpdump shows traffic flowing between the guacamole container and the LDAP > server. > Reverting back to version 1.1.0 "solved" the problem. > We suspect that the new LDAP configuration options changed a default behavior > to something that is incompatible with the Azure ADDS schema. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-942) MySQL JDBC contains an invalid SQL Query (no RDP Start possible)
[
https://issues.apache.org/jira/browse/GUACAMOLE-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153058#comment-17153058
]
Nick Couchman commented on GUACAMOLE-942:
-
[~mjumper]: I wonder if moving the "WHERE" part of the query over to the
"" syntax would resolve this? I'm not sure that it would work
in this situation, but I was using it recently for some of the changes in
GUACAMOLE-1123 and it seems like it has some amount of handling of situations
where the `WHERE` ends up with incorrect syntax or empty conditions.
> MySQL JDBC contains an invalid SQL Query (no RDP Start possible)
>
>
> Key: GUACAMOLE-942
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-942
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-mysql
>Affects Versions: 1.1.0
> Environment: CentOS 8
> Tomcat 9.0.30
> Guacamole 1.1.0, freshly upgraded from 0.9.14.
> LDAP backend
> JDBC MySQL connector 5.1.46 to MariaDB.
>Reporter: Stefan Bluhm
>Priority: Major
> Attachments: catalina.zip
>
>
> After logging in and selecting an RDP connection, the connection fails with:
>
> "The remote desktop server is currently not unreachable."...
>
> The catalona.out log shows the following error:
> {code:none}
> 17:02:02.435 [http-nio-8080-exec-3] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error:
> ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error
> in your SQL syntax; check the manual that corresponds to your MariaDB server
> version for the right syntax to use near 'AND
> (
> guacamole_connection_permission.entity_id = 7
> ' at line 19
> ### The error may exist in
> org/apache/guacamole/auth/jdbc/connection/ConnectionMapper.xml
> ### The error may involve defaultParameterMap
> ### The error occurred while setting parameters
> ### SQL: SELECT guacamole_connection.connection_id,
> guacamole_connection.connection_name, parent_id, protocol, max_connections,
> max_connections_per_user, proxy_hostname, proxy_port,
> proxy_encryption_method, connection_weight, failover_only, MAX(start_date) AS
> last_active FROM guacamole_connection JOIN guacamole_connection_permission ON
> guacamole_connection_permission.connection_id =
> guacamole_connection.connection_id LEFT JOIN guacamole_connection_history ON
> guacamole_connection_history.connection_id =
> guacamole_connection.connection_id WHERE guacamole_connection.connection_id
> IN AND ( guacamole_connection_permission.entity_id = ? ) AND permission =
> 'READ' GROUP BY guacamole_connection.connection_id; SELECT
> primary_connection_id, guacamole_sharing_profile.sharing_profile_id FROM
> guacamole_sharing_profile JOIN guacamole_sharing_profile_permission ON
> guacamole_sharing_profile_permission.sharing_profile_id =
> guacamole_sharing_profile.sharing_profile_id WHERE primary_connection_id IN
> AND ( entity_id = ? ) AND permission = 'READ'; SELECT
> guacamole_connection_attribute.connection_id, attribute_name, attribute_value
> FROM guacamole_connection_attribute JOIN guacamole_connection_permission ON
> guacamole_connection_permission.connection_id =
> guacamole_connection_attribute.connection_id WHERE
> guacamole_connection_attribute.connection_id IN AND ( entity_id = ? ) AND
> permission = 'READ';
> ### Cause: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You
> have an error in your SQL syntax; check the manual that corresponds to your
> MariaDB server version for the right syntax to use near 'AND
> (
> guacamole_connection_permission.entity_id = 7
> ' at line 19
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1102) suggestions
[ https://issues.apache.org/jira/browse/GUACAMOLE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138395#comment-17138395 ] Nick Couchman commented on GUACAMOLE-1102: -- [~leo87las]: Thanks for the clarification. Regarding both multiple roles and seeing recorded videos, see the issues I mentioned, as I think those will cover those use-cases. Regarding the PowerShell support, yes, that helps. I'm a little on the fence about whether we'd consider that something in scope for this project - on the one hand, it seems very similar to things like Kubernetes and SSH support; on the other hand, it seems like taking Guacamole in the direction of a more general remote access tool and not the "Clientless Remote Desktop" that it is meant to be. Setting side the question of whether that would be in-scope or not, I suspect that such a change would require a great deal of work, and would also depend upon the types of libraries and APIs available in the PowerShell code that Microsoft has released. I also have a fear that whatever libraries and APIs are available would require also pulling in Microsoft's .NET Core libraries. In the meantime, my usual practice is to install SSH on Windows servers and access them over SSH - and as Microsoft continues work on SSH for Windows, I'd suggest that might be a better path in general for Guacamole access to Windows Core servers than trying to put PowerShell support into Guacamole. But I'm open to the discussion :-). https://github.com/PowerShell/Win32-OpenSSH/releases > suggestions > > > Key: GUACAMOLE-1102 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1102 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.1.0 >Reporter: leo las >Priority: Minor > > * add multiple Roles of user permissions,such as auditing role . > * add support for PowerShell > * provide way to see recorded videos within guacamole webpage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1103) Typo mistake : the incorrect comment of a variable for the RDP setting
[
https://issues.apache.org/jira/browse/GUACAMOLE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1103:
-
Fix Version/s: (was: 1.2.0)
> Typo mistake : the incorrect comment of a variable for the RDP setting
> --
>
> Key: GUACAMOLE-1103
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1103
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, RDP
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Trivial
> Labels: easyfix
> Attachments: image-2020-06-17-19-04-05-018.png
>
> Original Estimate: 0.1h
> Remaining Estimate: 0.1h
>
> I found one issue in the source code of the guacamole server project.
> The issue is related to the comment of a variable for the RDP setting.
> The issue follows below:
> src/protocols/rdp/settings.h
> !image-2020-06-17-19-04-05-018.png!
> I think that the comment is changed to the following:
> {noformat}
> Whether SFTP should be enabled for the RDP connection.{noformat}
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1104) Remove the multiple calls of guac_rdp_disp_update_size() function in the guacamole server
[
https://issues.apache.org/jira/browse/GUACAMOLE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138639#comment-17138639
]
Nick Couchman commented on GUACAMOLE-1104:
--
Just a quick note, here - [~mjumper] may be able to provide more insight, but
if you look at the code for the guac_rdp_disp_update_size() function, you'll
see that it does its own checks as to whether it needs to continue and bails
out pretty early if no updates are requested, or if an update has already
occurred recently enough.
{code:c}
void guac_rdp_disp_update_size(guac_rdp_disp* disp,
guac_rdp_settings* settings, freerdp* rdp_inst) {
int width = disp->requested_width;
int height = disp->requested_height;
/* Do not update size if no requests have been received */
if (width == 0 || height == 0)
return;
guac_timestamp now = guac_timestamp_current();
/* Limit display update frequency */
if (now - disp->last_request <= GUAC_RDP_DISP_UPDATE_INTERVAL)
return;
{code}
That to say, there may be valid reasons why the call is left in there during
the normal loop.
> Remove the multiple calls of guac_rdp_disp_update_size() function in the
> guacamole server
> -
>
> Key: GUACAMOLE-1104
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1104
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-server, RDP
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Minor
> Labels: easyfix
> Attachments: image-2020-06-17-19-25-20-220.png,
> image-2020-06-17-19-32-30-990.png
>
>
> While using the guacamole server, I found that the
> guac_rdp_disp_update_size() function is unnecessarily several times called.
> This function is called when resizing the browser.
> The call stack of this function follows as below:
> !image-2020-06-17-19-25-20-220.png!
>
> This call is normal.
> But this function is continuously called in the loop of the
> guac_rdp_handle_connection() function regardless of the resizing of the
> browser.
> !image-2020-06-17-19-32-30-990.png!
>
> I removed the call and tested the relevant features such as resizing.
> It works well.
> So I think that we have to remove this call.
> If this issue is accepted by you, I want to fix it myself.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1102) suggestions
[
https://issues.apache.org/jira/browse/GUACAMOLE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138705#comment-17138705
]
Nick Couchman commented on GUACAMOLE-1102:
--
{quote}
I did find a "PSRP-Client-Library" project within the PowerShell github repo,
but it does not look promising:
{quote}
That may be the understatement of the year...they committed the README.md two
years ago...with not much content. LoL.
> suggestions
>
>
> Key: GUACAMOLE-1102
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1102
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
>Affects Versions: 1.1.0
>Reporter: leo las
>Priority: Minor
>
> * add multiple Roles of user permissions,such as auditing role .
> * add support for PowerShell
> * provide way to see recorded videos within guacamole webpage
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1104) Remove the multiple calls of guac_rdp_disp_update_size() function in the guacamole server
[ https://issues.apache.org/jira/browse/GUACAMOLE-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1104: - Fix Version/s: (was: 1.2.0) > Remove the multiple calls of guac_rdp_disp_update_size() function in the > guacamole server > - > > Key: GUACAMOLE-1104 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1104 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-server, RDP >Affects Versions: 1.1.0 >Reporter: Jimmy >Priority: Minor > Labels: easyfix > Attachments: image-2020-06-17-19-25-20-220.png, > image-2020-06-17-19-32-30-990.png > > > While using the guacamole server, I found that the > guac_rdp_disp_update_size() function is unnecessarily several times called. > This function is called when resizing the browser. > The call stack of this function follows as below: > !image-2020-06-17-19-25-20-220.png! > > This call is normal. > But this function is continuously called in the loop of the > guac_rdp_handle_connection() function regardless of the resizing of the > browser. > !image-2020-06-17-19-32-30-990.png! > > I removed the call and tested the relevant features such as resizing. > It works well. > So I think that we have to remove this call. > If this issue is accepted by you, I want to fix it myself. > Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1103) Typo mistake : the incorrect comment of a variable for the RDP setting
[
https://issues.apache.org/jira/browse/GUACAMOLE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138642#comment-17138642
]
Nick Couchman commented on GUACAMOLE-1103:
--
[~MyJimmy]:
You're definitely welcome to submit the pull request for the fix - we'd
appreciate the contribution! Guidelines for contributing are here:
http://guacamole.apache.org/open-source/
> Typo mistake : the incorrect comment of a variable for the RDP setting
> --
>
> Key: GUACAMOLE-1103
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1103
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, RDP
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Trivial
> Labels: easyfix
> Attachments: image-2020-06-17-19-04-05-018.png
>
> Original Estimate: 0.1h
> Remaining Estimate: 0.1h
>
> I found one issue in the source code of the guacamole server project.
> The issue is related to the comment of a variable for the RDP setting.
> The issue follows below:
> src/protocols/rdp/settings.h
> !image-2020-06-17-19-04-05-018.png!
> I think that the comment has to be changed to the following:
> {noformat}
> Whether SFTP should be enabled for the RDP connection.{noformat}
>
> If this issue is accepted by you, I want to fix it myself.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-513) Wake on LAN integration
[ https://issues.apache.org/jira/browse/GUACAMOLE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138747#comment-17138747 ] Nick Couchman commented on GUACAMOLE-513: - [~mjumper]: Fine with me. I've updated accordingly - if you think it's better to just remove the WoL wait time altogether, I can do that, too, although I think that having it as a configuration option is probably better than eliminating it. > Wake on LAN integration > --- > > Key: GUACAMOLE-513 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-513 > Project: Guacamole > Issue Type: New Feature >Reporter: Matt Blecha >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > I'm beating this horse back to life from the old issue tracker as I do > believe this is a rather important feature. > I know it was stated a day or two ago in the old issue tracker that there was > better justification necessary for this to be considered. Seeing as this > appears to be supported by both Microsoft in their RD Gateway and in Citrix's > gateway products since ~2014, there appears to be a fairly reasonable > justification for such a feature already in the business community, as well > as demand (seeing as Citrix made a fairly prominent announcement about it.) > > ===Begin TL;DR=== > > We love Guacamole in terms of performance (even when most of our users opted > to go the VNC route, despite having the RDP option made available to them), > mobile device operation, ease of use and administration and the pure > brain-dead simplicity of implementation and integration. (Thanks to the > developer who wrote that installation script, we were zero to deployed and > operating in less than 15 minutes, VM server spin-up included!) > That being said, we may be forced to abandon the whole infrastructure on > nearly 500 devices (and growing fast) in favor of a solution that is not as > efficient, yet provides one feature that we dearly need. > From my research (not as a coder, but serious DevOps experience) it's > relatively trivial to craft and broadcast a magic packet in Java (A GitHub > search yields several project with examples averaging about ~75 LOC, > including sanity checking.) Adding in a sort of "timeout hold-off" should > yield less than an additional 100 LOC, and user interface adjustments, > probably another few dozen or so. (Semi-educated guess.) All that would be > left then is to add an optional MAC address field to the proper table and > connection form, maybe a checkbox to enable WOL. > If WOL is simply too hard to code into Guacamole, then a more expansive set > of classes in the connection API would go a long way towards being able to > develop an extension. (From what I can see of the API docs, there appears to > be one call that would allow us to start the WOL process, but there are > several others necessary, for example; being able to hold off the connection > timeout while the remote station completes waking up. We do, after all, want > this to be a seamless process to the end user.) > > ===End TL;DR=== > > It seems to me that there are several reasonable use cases for such a > feature, even if it is an extension and not a core component, though it seems > this would probably be easier to merge into core as it would work more > elegantly with some database integration, which I did not see in the API > docs. (Admittedly, might not have looked closely enough, and I don't really > code Java, so I'm not sure what's in that section.) > I do think this would go a long way in scoring a decent amount of points for > this project. It seems like there are others out there who support such a > feature, hacky as it may be in some products. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1105) Add support to disable auto-complete on credential fields
[ https://issues.apache.org/jira/browse/GUACAMOLE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1105: - Affects Version/s: (was: 1.0.0) > Add support to disable auto-complete on credential fields > - > > Key: GUACAMOLE-1105 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1105 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Reporter: Tushar Jain >Priority: Minor > > Looking for a way to disable storage of user credentials in the browser. The > user can select to save the credentials in the browser accidently or > unknowingly. And if it is a shared computer, anyone who opens the login page > again, can just select the username and the password automatically gets > displayed in the password box. Want to disable this auto-complete feature > from Guacamole itself, something similar to what happens on net banking sites -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1105) Add support to disable auto-complete on credential fields
[ https://issues.apache.org/jira/browse/GUACAMOLE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1105: - Summary: Add support to disable auto-complete on credential fields (was: Disable browser caching of user credentials) > Add support to disable auto-complete on credential fields > - > > Key: GUACAMOLE-1105 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1105 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Affects Versions: 1.0.0 >Reporter: Tushar Jain >Priority: Minor > > Looking for a way to disable storage of user credentials in the browser. The > user can select to save the credentials in the browser accidently or > unknowingly. And if it is a shared computer, anyone who opens the login page > again, can just select the username and the password automatically gets > displayed in the password box. Want to disable this auto-complete feature > from Guacamole itself, something similar to what happens on net banking sites -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1102) suggestions
[
https://issues.apache.org/jira/browse/GUACAMOLE-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138704#comment-17138704
]
Nick Couchman commented on GUACAMOLE-1102:
--
{quote}
Nothing needs to be changed or implemented within Guacamole for that to work,
and I expect it should work quite well.
{quote}
>From my experience using PowerShell over SSH, the only issue I've run into is
>that the SSH implementation doesn't really handle varying terminal widths very
>well - it tends to be very picky about having terminals sized to the old "cmd"
>settings, and using more customized values tends to result in very odd
>behavior when the lines wrap. I suspect this has been reported somewhere
>along the way, and that they'll work it out, eventually, but it can make for a
>interesting experience trying to use PS over SSH :-).
> suggestions
>
>
> Key: GUACAMOLE-1102
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1102
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
>Affects Versions: 1.1.0
>Reporter: leo las
>Priority: Minor
>
> * add multiple Roles of user permissions,such as auditing role .
> * add support for PowerShell
> * provide way to see recorded videos within guacamole webpage
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1106) Improper log message when there is no clipboard data
[ https://issues.apache.org/jira/browse/GUACAMOLE-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17138727#comment-17138727 ] Nick Couchman commented on GUACAMOLE-1106: -- [~MyJimmy]: You're certainly welcome to submit the changes you think may be applicable and we'll review them to see if there is a valid fix. I will say that data is frequently copied to the clipboard in the background. I use Linux as my client O/S, and the clipboard is populated when you select text. Windows does not generally behave that way, though there are some exceptions, but there still may be times when some application or another populates data onto the clipboard in the background. Also, if you have multiple remote sessions running Guacamole and one of those sessions copies data onto the clipboard, it can be updated for the other sessions, as well, which would cause this message. > Improper log message when there is no clipboard data > > > Key: GUACAMOLE-1106 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1106 > Project: Guacamole > Issue Type: Bug > Components: guacamole-server, RDP >Affects Versions: 1.1.0 >Reporter: Jimmy >Priority: Minor > Labels: log > Fix For: 1.2.0 > > Attachments: image-2020-06-17-21-23-56-419.png > > > I can see the following log message on the console of the guacamole server > whenever I select another application other than the browser: > !image-2020-06-17-21-23-56-419.png! > Especially, I didn't copy any text to the clipboard, but this log message is > displayed. > I think that we need to decide whether the guacamole server shows this log > message or not based on certain criteria such as the length of the clipboard. > If this issue is accepted by you, I want to fix it myself. > Thanks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-1103) Typo mistake : the incorrect comment of a variable for the RDP setting
[
https://issues.apache.org/jira/browse/GUACAMOLE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-1103.
--
Resolution: Fixed
Thanks [~MyJimmy]!
> Typo mistake : the incorrect comment of a variable for the RDP setting
> --
>
> Key: GUACAMOLE-1103
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1103
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, RDP
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Trivial
> Labels: easyfix
> Attachments: image-2020-06-17-19-04-05-018.png
>
> Original Estimate: 0.1h
> Remaining Estimate: 0.1h
>
> I found one issue in the source code of the guacamole server project.
> The issue is related to the comment of a variable for the RDP setting.
> The issue follows below:
> src/protocols/rdp/settings.h
> !image-2020-06-17-19-04-05-018.png!
> I think that the comment has to be changed to the following:
> {noformat}
> Whether SFTP should be enabled for the RDP connection.{noformat}
>
> If this issue is accepted by you, I want to fix it myself.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1103) Typo mistake : the incorrect comment of a variable for the RDP setting
[
https://issues.apache.org/jira/browse/GUACAMOLE-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-1103:
-
Fix Version/s: 1.3.0
> Typo mistake : the incorrect comment of a variable for the RDP setting
> --
>
> Key: GUACAMOLE-1103
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1103
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-server, RDP
>Affects Versions: 1.1.0
>Reporter: Jimmy
>Priority: Trivial
> Labels: easyfix
> Fix For: 1.3.0
>
> Attachments: image-2020-06-17-19-04-05-018.png
>
> Original Estimate: 0.1h
> Remaining Estimate: 0.1h
>
> I found one issue in the source code of the guacamole server project.
> The issue is related to the comment of a variable for the RDP setting.
> The issue follows below:
> src/protocols/rdp/settings.h
> !image-2020-06-17-19-04-05-018.png!
> I think that the comment has to be changed to the following:
> {noformat}
> Whether SFTP should be enabled for the RDP connection.{noformat}
>
> If this issue is accepted by you, I want to fix it myself.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1059) Tolerate RDP protocol violations where possible
[ https://issues.apache.org/jira/browse/GUACAMOLE-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141449#comment-17141449 ] Nick Couchman commented on GUACAMOLE-1059: -- [~mjumper]: Do we have anything else we need to close out for this one - documentation or other changes that need to be made? > Tolerate RDP protocol violations where possible > --- > > Key: GUACAMOLE-1059 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1059 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Nick Couchman >Assignee: Nick Couchman >Priority: Major > Fix For: 1.2.0 > > > While FreeRDP internally handles most details of the RDP protocol, and makes > its own decisions regarding what to tolerate vs. what to consider a fatal > error, some low-level protocol handling is Guacamole-specific and within our > scope of control. > RDP protocol violations are relatively common, even within the standard > Windows implementation, which can lead to unexpected connection failures with > otherwise common RDP servers (see GUACAMOLE-1028). In the interest of > connection stability, Guacamole should prefer to log a warning and trudge > onward, resorting to fatal errors only where absolutely necessary. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-474) Allow file upload and download to be enabled separately
[ https://issues.apache.org/jira/browse/GUACAMOLE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-474. - Resolution: Implemented Implementation and documentation completed. > Allow file upload and download to be enabled separately > --- > > Key: GUACAMOLE-474 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-474 > Project: Guacamole > Issue Type: New Feature > Components: guacamole >Reporter: Amarjeet Singh >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.2.0 > > > It would be helpful if file downloads could be disabled while still allowing > file uploads. In a classroom setting, it would be beneficial to allow > students to upload files to a remote VM, but disable download of files like > binary license files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1105) Add support to disable auto-complete on credential fields
[ https://issues.apache.org/jira/browse/GUACAMOLE-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143196#comment-17143196 ] Nick Couchman commented on GUACAMOLE-1105: -- [~tusharjain]: No, it will not be in version 1.2.0 - it hasn't even been started, yet. Scope for 1.2.0 is fixed and there will be no further additions to it other than identified regressions from 1.1.0. > Add support to disable auto-complete on credential fields > - > > Key: GUACAMOLE-1105 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1105 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Reporter: Tushar Jain >Priority: Minor > > Looking for a way to disable storage of user credentials in the browser. The > user can select to save the credentials in the browser accidently or > unknowingly. And if it is a shared computer, anyone who opens the login page > again, can just select the username and the password automatically gets > displayed in the password box. Want to disable this auto-complete feature > from Guacamole itself, something similar to what happens on net banking sites -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-300) Support posixGroup in LDAP Authentication and Group-based Session Admission
[ https://issues.apache.org/jira/browse/GUACAMOLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-300. - Resolution: Implemented Changes and documentation merged. > Support posixGroup in LDAP Authentication and Group-based Session Admission > --- > > Key: GUACAMOLE-300 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-300 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-ldap > Environment: Oracle Solaris 11.3.19.5.0, Apache Tomcat 8.5.9, > OpenLDAP 2.4.30, LDAP users are organized using the posixGroup scheme. >Reporter: Steffen Moser >Priority: Minor > Fix For: 1.2.0 > > Attachments: LDAP-posixGroup-support_SteffenMoser-20170514.patch > > > Recently, the auth-ldap module was extended by the ability to grant access to > remote terminal connections based on existing LDAP groups using the seeAlso > attribute in Guacamole's LDAP-based configuration settings. This is a great > feature if you've to manage a lot of users which are already organized in > LDAP groups. It works well as long as the groups are of the scheme > groupOfNames. As we have decided for posixGroup (due to other tools' > requirements), we currently cannot use the feature and still have to list all > users individually in the Guacamole remote service configuration. While this > could be scripted easily, it is still a work-around which makes the > administration work unnecessarily complex. > A better solution would be to support both schemes, posixGroup and > groupOfNames. > The attached patch will extend the user lookup code by the ability to search > not only through the groupOfNames but also through the posixGroup scheme. The > piece of code seems to work with both schemes in my tests successfully, I am > not sure if there are any pitfalls when just combining the possible results. > Maybe introducing a configuration flag to choose whether searching posixGroup > or groupOfNames would be a better approach. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-728) Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not Allowed
[
https://issues.apache.org/jira/browse/GUACAMOLE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-728.
-
Resolution: Fixed
All changes and documentation merged.
> Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not
> Allowed
> -
>
> Key: GUACAMOLE-728
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-728
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-auth-jdbc-mysql
>Affects Versions: 1.0.0
>Reporter: David
>Assignee: Nick Couchman
>Priority: Major
> Fix For: 1.2.0
>
>
> When running the guacamole docker image linked to a mysql8 docker image, I'm
> experiencing an error in the logs that says:
> {code:none}
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> 04:24:15.832 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error:
> ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> ### The error may exist in org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> ### The error may involve
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> ### The error occurred while executing a query
> ### Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> {code}
> I'm not sure how to get around this, but it's keeping me from using
> guacamole. :(
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-728) Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not Allowed
[
https://issues.apache.org/jira/browse/GUACAMOLE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-728.
-
Resolution: Fixed
> Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not
> Allowed
> -
>
> Key: GUACAMOLE-728
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-728
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-auth-jdbc-mysql
>Affects Versions: 1.0.0
>Reporter: David
>Assignee: Nick Couchman
>Priority: Major
> Fix For: 1.2.0
>
>
> When running the guacamole docker image linked to a mysql8 docker image, I'm
> experiencing an error in the logs that says:
> {code:none}
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> 04:24:15.832 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error:
> ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> ### The error may exist in org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> ### The error may involve
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> ### The error occurred while executing a query
> ### Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> {code}
> I'm not sure how to get around this, but it's keeping me from using
> guacamole. :(
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1111) Guacamole gives error after updating Tomcat
[ https://issues.apache.org/jira/browse/GUACAMOLE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145758#comment-17145758 ] Nick Couchman commented on GUACAMOLE-: -- [~michael.vasile]: Please start asking for help on the mailing list: http://guacamole.apache.org/support/ It is very likely the issue you've encountered is not a bug, but a configuration or environment issue. We're happy to help you out over there, and your request will reach a larger community: http://guacamole.apache.org/faq/#probably-not-a-bug If you are not seeing the detail you need in catalina.out, then you might need to increase the level of logging: http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging > Guacamole gives error after updating Tomcat > --- > > Key: GUACAMOLE- > URL: https://issues.apache.org/jira/browse/GUACAMOLE- > Project: Guacamole > Issue Type: Bug > Components: guacamole, guacd >Affects Versions: 1.1.0 >Reporter: Michael Vasile >Priority: Major > Labels: error, tomcat > Attachments: image-2020-06-25-12-05-14-110.png > > > I have Guacamole installed on a RHEL 7 server. After installing an update to > Tomcat, Guacamole has broken and I get this error when trying to access it. > !image-2020-06-25-12-05-14-110.png! > I tried checking catalina.out and did not see any errors in the logs. Not > sure if there's anywhere else that would need to be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1111) Guacamole gives error after updating Tomcat
[ https://issues.apache.org/jira/browse/GUACAMOLE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-: - Priority: Minor (was: Major) > Guacamole gives error after updating Tomcat > --- > > Key: GUACAMOLE- > URL: https://issues.apache.org/jira/browse/GUACAMOLE- > Project: Guacamole > Issue Type: Bug > Components: guacamole, guacd >Affects Versions: 1.1.0 >Reporter: Michael Vasile >Priority: Minor > Labels: error, tomcat > Attachments: image-2020-06-25-12-05-14-110.png > > > I have Guacamole installed on a RHEL 7 server. After installing an update to > Tomcat, Guacamole has broken and I get this error when trying to access it. > !image-2020-06-25-12-05-14-110.png! > I tried checking catalina.out and did not see any errors in the logs. Not > sure if there's anywhere else that would need to be checked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1024) Enabling gucamole debug logs without restarting docker container
[ https://issues.apache.org/jira/browse/GUACAMOLE-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1024. Resolution: Invalid > Enabling gucamole debug logs without restarting docker container > > > Key: GUACAMOLE-1024 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1024 > Project: Guacamole > Issue Type: Wish > Components: guacd >Reporter: Abhijeet Jha >Priority: Minor > > Is there a way by which guacamole debug logs can be enabled without > restarting docker container. Right now we have to add environment variable in > docker file which triggers a new release and subsequently restart is required. > Can we control this behavior of enabling debugs by some configuration > parameter where restart can be avoided completely. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-474) Allow file upload and download to be enabled separately
[ https://issues.apache.org/jira/browse/GUACAMOLE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145841#comment-17145841 ] Nick Couchman commented on GUACAMOLE-474: - [~mjumper]: Eeeksorry about that. I have some changes going to address, unless you've already got it covered? > Allow file upload and download to be enabled separately > --- > > Key: GUACAMOLE-474 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-474 > Project: Guacamole > Issue Type: New Feature > Components: guacamole, RDP, SSH, VNC >Reporter: Amarjeet Singh >Assignee: Mike Jumper >Priority: Minor > Fix For: 1.2.0 > > > It would be helpful if file downloads could be disabled while still allowing > file uploads. In a classroom setting, it would be beneficial to allow > students to upload files to a remote VM, but disable download of files like > binary license files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GUACAMOLE-1081) option to convert usernames to all lowercase
[
https://issues.apache.org/jira/browse/GUACAMOLE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144576#comment-17144576
]
Nick Couchman edited comment on GUACAMOLE-1081 at 6/25/20, 7:17 PM:
[~kangaroo22]: I figured out what's going on with this - turns out the modifier
is getting canonicalized along with the rest of the token, so:
{code}
${GUAC_USERNAME:lower}
{code}
becomes:
{code}
${GUAC_USERNAME:LOWER}
{code}
and the code didn't taken that into account. I've submitted the pull request
so that it pays attention to and both "lower" and "LOWER" should behave the
same.
was (Author: nick.couch...@yahoo.com):
[~kangaroo22]: I figured out what's going on with this - turns out the modifier
is getting canonicalized along with the rest of the token, so:
{code}
${GUAC_USERNAME:lower}
{code}
becomes:
{code}
${GAUC_USERNAME:LOWER}
{code}
and the code didn't taken that into account. I've submitted the pull request
so that it pays attention to and both "lower" and "LOWER" should behave the
same.
> option to convert usernames to all lowercase
>
>
> Key: GUACAMOLE-1081
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1081
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, guacamole-ext
>Reporter: Jason Keltz
>Assignee: Nick Couchman
>Priority: Minor
> Fix For: 1.3.0
>
>
> When the user logs into Guac with parts of their username in uppercase, the
> login to Guac is successful, but then subsequent login to Linux systems fails
> because the username is case sensitive. It would be useful to have an option
> in Guacamole to convert usernames to lowercase or uppercase before passing on
> to the systems.
> One possible suggestion from Nick on the mailing list was something like this:
>
> ${GUAC_USERNAME} - Pass through as entered
> ${GUAC_USERNAME:lower} - Convert string to lower-case
> ${GUAC_USERNAME:upper} - Convert string to upper-case
>
> This would work very well.
> I would be likewise happy with a solution that let me set a default somewhere
> (in my case, all lowercase).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (GUACAMOLE-728) Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not Allowed
[
https://issues.apache.org/jira/browse/GUACAMOLE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman reopened GUACAMOLE-728:
-
Addressing changes to default behavior
> Docker image unable to connect to MySQL8 docker: Public Key Retrieval Not
> Allowed
> -
>
> Key: GUACAMOLE-728
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-728
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation, guacamole-auth-jdbc-mysql
>Affects Versions: 1.0.0
>Reporter: David
>Assignee: Nick Couchman
>Priority: Major
> Fix For: 1.2.0
>
>
> When running the guacamole docker image linked to a mysql8 docker image, I'm
> experiencing an error in the logs that says:
> {code:none}
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> Fri Feb 08 04:24:15 UTC 2019 WARN: Establishing SSL connection without
> server's identity verification is not recommended. According to MySQL
> 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established
> by default if explicit option isn't set. For compliance with existing
> applications not using SSL the verifyServerCertificate property is set to
> 'false'. You need either to explicitly disable SSL by setting useSSL=false,
> or set useSSL=true and provide truststore for server certificate verification.
> 04:24:15.832 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper -
> Unexpected internal error:
> ### Error querying database. Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> ### The error may exist in org/apache/guacamole/auth/jdbc/user/UserMapper.xml
> ### The error may involve
> org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
> ### The error occurred while executing a query
> ### Cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Public
> Key Retrieval is not allowed
> {code}
> I'm not sure how to get around this, but it's keeping me from using
> guacamole. :(
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1107) "allowed-languages" property incorrectly documented as "available-languages"
[
https://issues.apache.org/jira/browse/GUACAMOLE-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145785#comment-17145785
]
Nick Couchman commented on GUACAMOLE-1107:
--
[~71SRCK]: I do not doubt that you are seeing that behavior; just stating that
I cannot reproduce it at all, let alone consistently, so, if a bug does exist
it is a little more nuanced than just using the OSK while the browser developer
tools are running. The bug could be in the browser itself (crashing a
JavaScript process, for example), or in some other combination of of factors
within your environment. My follow-up questions would be:
* Can you reproduce the behavior on multiple computers with multiple browsers?
* What browser and client O/S are you using?
* What display protocol are you using?
* Have you tried with other Guacamole versions, both Guacamole Client and
Server?
> "allowed-languages" property incorrectly documented as "available-languages"
>
>
> Key: GUACAMOLE-1107
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1107
> Project: Guacamole
> Issue Type: Bug
> Components: Documentation
>Reporter: Ji Shoukai
>Priority: Trivial
>
> The Guacamole web application allows the display languages presented to the
> user to be limited through specifying [the {{allowed-languages}}
> property|https://github.com/apache/guacamole-client/blob/577eca819f67d17fab71745519421dca1eb57b01/guacamole/src/main/java/org/apache/guacamole/extension/LanguageResourceService.java#L77-L88].
> This property is incorrectly documented in the manual as
> [{{available-languages}}|http://guacamole.apache.org/doc/1.1.0/gug/configuring-guacamole.html#initial-setup].
> The documentation should be corrected to note the correct property name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
