[jira] [Commented] (GUACAMOLE-717) LDAP authentication fails if search result count exceeds ldap-max-search-result

2019-01-25 Thread Nick Couchman (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752891#comment-16752891
 ] 

Nick Couchman commented on GUACAMOLE-717:
-

I think this might be a duplicate of GUACAMOLE-702??

> LDAP authentication fails if search result count exceeds 
> ldap-max-search-result
> ---
>
> Key: GUACAMOLE-717
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-717
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-client
>Affects Versions: 1.0.0
>Reporter: Joel Best
>Priority: Minor
>
> If the search results from an LDAP search exceed ldap-max-search-results, the 
> search will fail and the user will receive an error on login. The logs do not 
> show any indication of what the problem is.
> After troubleshooting, I've determined that the LDAPSearchResults.next() 
> function returns an LDAPException "Sizelimit Exceeded". In 
> ObjectQueryService.search(), this is not handled within the immediate 
> try/catch block so the other valid results are not returned to the calling 
> function. The fix is to also catch LDAPException when catching 
> LDAPReferralException.
> Pull request is incoming.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GUACAMOLE-312) VNC over SSH

2019-01-25 Thread Nick Couchman (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752890#comment-16752890
 ] 

Nick Couchman commented on GUACAMOLE-312:
-

I was thinking it would doable by having libssh2 stand up a port-forward, and 
then redirecting the traffic through that port forward.  There's nothing 
built-in to libssh2 to handle the port forwarding - it would have to be coded 
using, most likely, the same socket approach you mention, here, but doing so 
would allow for forwarding without worrying about whether the VNC (or RDP, or 
Telnet) library supported sockets, right?

> VNC over SSH
> 
>
> Key: GUACAMOLE-312
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-312
> Project: Guacamole
>  Issue Type: New Feature
>  Components: VNC
>Reporter: Michael Jumper
>Priority: Minor
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from 
> [GUAC-223|https://glyptodon.org/jira/browse/GUAC-223], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> It would be useful to provide access to VNC over SSH as an option.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Rui Wang (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752879#comment-16752879
 ] 

Rui Wang commented on GUACAMOLE-719:


Found a similar issue here:

https://jira.glyptodon.com/projects/GUAC/issues/GUAC-1510

> Guacamole: Multiple simultaneous vnc connections over websocket close each 
> other
> 
>
> Key: GUACAMOLE-719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-719
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-common, guacd
>Affects Versions: 0.9.14
>Reporter: Rui Wang
>Priority: Major
>
> We are using guacamole to access remote desktop in web-browser. We try to use 
> websocket-tunnel for better performance, but if I open two tab in my browser 
> connecting to same vnc server with different ports through same guacd server, 
> one page get frozen(websocket stop send/receive any messages), the other get 
> error like: 776 and disconnected. And we can connect to these two vnc servers 
> using vnc-viewer direclty after browser vnc frozen/disconnected.
> Seems guacd will abort/kill one after another. It's only happending if we use 
> webscoket, using httpeServlet tunnel seems do not have such probelm.
> Anyone encounter similar issue? Here are my setup.
>  # guacamole-js was used in web side.
>  # We use x11vnc, guacd installed with same linux box
>  # We developed two endpoints use spring-boot: websocket-tunnel by extending 
> GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
> GuacamoleHTTPTunnelServlet
> guacd log here:
> {code:java}
> Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
> Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
> "$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
> Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 
> 3.8 (viewer 3.8)
> Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
> Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
> Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
> list)
> Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
> Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
> Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
> Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
> Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using 
> protocol version 3.8
> Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
> Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
> Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
> pixel.
> Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 
> blue 255, shift red 16 green 8 blue 0
> Jan 25 04:32:58 vnchost guacd[105232]: Starting client
> Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
> flags)
> Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 08:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 10:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 18:     -   
>  0004
> Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
> flags)
> Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 08:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 10:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 18:     -   
>  0004
> Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
> (LibVNCServer 0.9.9)"
> Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
> Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
> "$6fd98484-1dd0-4c66-aa04-6c358cd30548"
> Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 
> 3.8 (viewer 3.8)
> Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
> Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
> Jan 25 04:36:29 vnchost guacd[105538]: Selecting security type 1 (0/1 in the 
> list)
> Jan 25 04:36:29 vnchost guacd[105538]: Selected Security Scheme 1
> Jan 25 04:36:29 vnchost guacd[105538]: No authentication needed
> Jan 25 04:36:29 vnchost guacd[105538]: VNC authentication succeeded
> Jan 25 04:36:29 vnchost guacd[105538]: Desktop name "vnchost:2"
> Jan 25 04:36:29 vnchost guacd[105538]: Connected to VNC server, using 
> protocol version 3.8
> Jan 25 04:36:29 vnchost guacd[105538]: VNC server default format:
> Jan 25 04:36:29 vnchost 

[jira] [Closed] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Michael Jumper (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jumper closed GUACAMOLE-719.

Resolution: Invalid

Hi [~phantomblue],

If you're having network issues like described here, please bring your question 
to the mailing list. We and the rest of the community can attempt to assist 
there. As mentioned in the FAQ, [the more fundamental an issue is, the less 
likely it is to be a bug|http://guacamole.apache.org/faq/#probably-not-a-bug], 
and in this case it's safe to say that VNC and WebSocket are not fundamentally 
broken in 0.9.14 nor the latest 1.0.0 release.

Please also be sure to retry against the latest release (1.0.0) to make sure 
that what you're seeing is not due to some underlying issue that has actually 
already been fixed.

> Guacamole: Multiple simultaneous vnc connections over websocket close each 
> other
> 
>
> Key: GUACAMOLE-719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-719
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-common, guacd
>Affects Versions: 0.9.14
>Reporter: Rui Wang
>Priority: Major
>
> We are using guacamole to access remote desktop in web-browser. We try to use 
> websocket-tunnel for better performance, but if I open two tab in my browser 
> connecting to same vnc server with different ports through same guacd server, 
> one page get frozen(websocket stop send/receive any messages), the other get 
> error like: 776 and disconnected. And we can connect to these two vnc servers 
> using vnc-viewer direclty after browser vnc frozen/disconnected.
> Seems guacd will abort/kill one after another. It's only happending if we use 
> webscoket, using httpeServlet tunnel seems do not have such probelm.
> Anyone encounter similar issue? Here are my setup.
>  # guacamole-js was used in web side.
>  # We use x11vnc, guacd installed with same linux box
>  # We developed two endpoints use spring-boot: websocket-tunnel by extending 
> GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
> GuacamoleHTTPTunnelServlet
> guacd log here:
> {code:java}
> Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
> Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
> "$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
> Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 
> 3.8 (viewer 3.8)
> Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
> Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
> Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
> list)
> Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
> Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
> Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
> Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
> Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using 
> protocol version 3.8
> Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
> Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
> Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
> pixel.
> Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 
> blue 255, shift red 16 green 8 blue 0
> Jan 25 04:32:58 vnchost guacd[105232]: Starting client
> Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
> flags)
> Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 08:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 10:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 18:     -   
>  0004
> Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
> flags)
> Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 08:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 10:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 18:     -   
>  0004
> Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
> (LibVNCServer 0.9.9)"
> Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
> Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
> "$6fd98484-1dd0-4c66-aa04-6c358cd30548"
> Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 
> 3.8 (viewer 3.8)
> Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
> Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
> Jan 25 

[jira] [Updated] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Rui Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Wang updated GUACAMOLE-719:
---
Component/s: guacamole-common

> Guacamole: Multiple simultaneous vnc connections over websocket close each 
> other
> 
>
> Key: GUACAMOLE-719
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-719
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-common, guacd
>Affects Versions: 0.9.14
>Reporter: Rui Wang
>Priority: Major
>
> We are using guacamole to access remote desktop in web-browser. We try to use 
> websocket-tunnel for better performance, but if I open two tab in my browser 
> connecting to same vnc server with different ports through same guacd server, 
> one page get frozen(websocket stop send/receive any messages), the other get 
> error like: 776 and disconnected. And we can connect to these two vnc servers 
> using vnc-viewer direclty after browser vnc frozen/disconnected.
> Seems guacd will abort/kill one after another. It's only happending if we use 
> webscoket, using httpeServlet tunnel seems do not have such probelm.
> Anyone encounter similar issue? Here are my setup.
>  # guacamole-js was used in web side.
>  # We use x11vnc, guacd installed with same linux box
>  # We developed two endpoints use spring-boot: websocket-tunnel by extending 
> GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
> GuacamoleHTTPTunnelServlet
> guacd log here:
> {code:java}
> Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
> Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
> "$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
> Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 
> 3.8 (viewer 3.8)
> Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
> Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
> Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
> list)
> Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
> Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
> Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
> Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
> Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using 
> protocol version 3.8
> Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
> Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
> Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
> pixel.
> Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 
> blue 255, shift red 16 green 8 blue 0
> Jan 25 04:32:58 vnchost guacd[105232]: Starting client
> Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
> flags)
> Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 08:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 10:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 18:     -   
>  0004
> Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
> flags)
> Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 08:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 10:     -   
>  
> Jan 25 04:32:58 vnchost guacd[105232]: 18:     -   
>  0004
> Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
> (LibVNCServer 0.9.9)"
> Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
> Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
> "$6fd98484-1dd0-4c66-aa04-6c358cd30548"
> Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 
> 3.8 (viewer 3.8)
> Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
> Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
> Jan 25 04:36:29 vnchost guacd[105538]: Selecting security type 1 (0/1 in the 
> list)
> Jan 25 04:36:29 vnchost guacd[105538]: Selected Security Scheme 1
> Jan 25 04:36:29 vnchost guacd[105538]: No authentication needed
> Jan 25 04:36:29 vnchost guacd[105538]: VNC authentication succeeded
> Jan 25 04:36:29 vnchost guacd[105538]: Desktop name "vnchost:2"
> Jan 25 04:36:29 vnchost guacd[105538]: Connected to VNC server, using 
> protocol version 3.8
> Jan 25 04:36:29 vnchost guacd[105538]: VNC server default format:
> Jan 25 04:36:29 vnchost guacd[105538]:  32 bits per pixel.
> Jan 25 04:36:29 vnchost guacd[105538]:  Least significant byte 

[jira] [Updated] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Rui Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Wang updated GUACAMOLE-719:
---
Description: 
We are using guacamole to access remote desktop in web-browser. We try to use 
websocket-tunnel for better performance, but if I open two tab in my browser 
connecting to same vnc server with different ports through same guacd server, 
one page get frozen(websocket stop send/receive any messages), the other get 
error like: 776 and disconnected. And we can connect to these two vnc servers 
using vnc-viewer direclty after browser vnc frozen/disconnected.

Seems guacd will abort/kill one after another. It's only happending if we use 
webscoket, using httpeServlet tunnel seems do not have such probelm.

Anyone encounter similar issue? Here are my setup.
 # guacamole-js was used in web side.
 # We use x11vnc, guacd installed with same linux box
 # We developed two endpoints use spring-boot: websocket-tunnel by extending 
GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
GuacamoleHTTPTunnelServlet

guacd log here:
{code:java}
Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
"$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:32:58 vnchost guacd[105232]: Starting client
Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
(LibVNCServer 0.9.9)"

Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
"$6fd98484-1dd0-4c66-aa04-6c358cd30548"
Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
Jan 25 04:36:29 vnchost guacd[105538]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:36:29 vnchost guacd[105538]: Selected Security Scheme 1
Jan 25 04:36:29 vnchost guacd[105538]: No authentication needed
Jan 25 04:36:29 vnchost guacd[105538]: VNC authentication succeeded
Jan 25 04:36:29 vnchost guacd[105538]: Desktop name "vnchost:2"
Jan 25 04:36:29 vnchost guacd[105538]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:36:29 vnchost guacd[105538]: VNC server default format:
Jan 25 04:36:29 vnchost guacd[105538]:  32 bits per pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  Least significant byte first in each 
pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:36:29 vnchost guacd[105538]: Starting client
Jan 25 04:36:29 vnchost guacd[105538]: client2server supported messages (bit 
flags)
Jan 25 04:36:29 vnchost guacd[105538]: 00: 00ff 0081   -    

Jan 25 04:36:29 vnchost guacd[105538]: 08:     -    

Jan 25 04:36:29 vnchost guacd[105538]: 10:     -    

Jan 25 04:36:29 vnchost guacd[105538]: 18:     -    
0004
Jan 25 04:36:29 vnchost 

[jira] [Updated] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Rui Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Wang updated GUACAMOLE-719:
---
Description: 
We are using guacamole to access remote desktop in web-browser. We try to use 
websocket-tunnel for better performance, but if I open two tab in my browser 
connecting to same vnc server with different ports through same guacd server, 
one page get frozen(websocket stop send/receive any messages), the other get 
error like: 776 and disconnected. And we can connect to these two vnc servers 
using vnc-viewer direclty after browser vnc frozen/disconnected.

Seems guacd will abort/kill one after another. It's only happending if we use 
webscoket, using httpeServlet tunnel seems do not have such probelm.

Anyone encounter similar issue? Here are my setup.
 # guacamole-js was used in web side.
 # We use x11vnc, guacd installed with same linux box
 # We developed two endpoints use spring-boot: websocket-tunnel by extending 
GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
GuacamoleHTTPTunnelServlet

guacd log here:
{code:java}
Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
"$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:32:58 vnchost guacd[105232]: Starting client
Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
(LibVNCServer 0.9.9)"

Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
"$6fd98484-1dd0-4c66-aa04-6c358cd30548"
Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
Jan 25 04:36:29 vnchost guacd[105538]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:36:29 vnchost guacd[105538]: Selected Security Scheme 1
Jan 25 04:36:29 vnchost guacd[105538]: No authentication needed
Jan 25 04:36:29 vnchost guacd[105538]: VNC authentication succeeded
Jan 25 04:36:29 vnchost guacd[105538]: Desktop name "vnchost:2"
Jan 25 04:36:29 vnchost guacd[105538]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:36:29 vnchost guacd[105538]: VNC server default format:
Jan 25 04:36:29 vnchost guacd[105538]:  32 bits per pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  Least significant byte first in each 
pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:36:29 vnchost guacd[105538]: Starting client
Jan 25 04:36:29 vnchost guacd[105538]: client2server supported messages (bit 
flags)
Jan 25 04:36:29 vnchost guacd[105538]: 00: 00ff 0081   -    

Jan 25 04:36:29 vnchost guacd[105538]: 08:     -    

Jan 25 04:36:29 vnchost guacd[105538]: 10:     -    

Jan 25 04:36:29 vnchost guacd[105538]: 18:     -    
0004
Jan 25 04:36:29 vnchost 

[jira] [Created] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Rui Wang (JIRA)
Rui Wang created GUACAMOLE-719:
--

 Summary: Guacamole: Multiple simultaneous vnc connections over 
websocket close each other
 Key: GUACAMOLE-719
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-719
 Project: Guacamole
  Issue Type: Bug
  Components: guacd
Affects Versions: 0.9.14
Reporter: Rui Wang


 
{code:java}
 {code}
We are using guacamole to access remote desktop in web-browser. We try to use 
websocket-tunnel for better performance, but if I open two tab in my browser 
connecting to same vnc server with different ports through same guacd server, 
one page get frozen(websocket stop send/receive any messages), the other get 
error like: 776 and disconnected. And we can connect to these two vnc servers 
using vnc-viewer direclty after browser vnc frozen/disconnected.

 

Seems guacd will abort/kill one after another. It's only happending if we use 
webscoket, using httpeServlet tunnel seems do not have such probelm.

Anyone encounter similar issue? Here are my setup.
 # guacamole-js was used in web side.
 # We use x11vnc, guacd installed with same linux box
 # We developed two endpoints use spring-boot: websocket-tunnel by extending 
GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
GuacamoleHTTPTunnelServlet

guacd log here:

 
{code:java}
Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
"$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:32:58 vnchost guacd[105232]: Starting client
Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
(LibVNCServer 0.9.9)"

Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
"$6fd98484-1dd0-4c66-aa04-6c358cd30548"
Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
Jan 25 04:36:29 vnchost guacd[105538]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:36:29 vnchost guacd[105538]: Selected Security Scheme 1
Jan 25 04:36:29 vnchost guacd[105538]: No authentication needed
Jan 25 04:36:29 vnchost guacd[105538]: VNC authentication succeeded
Jan 25 04:36:29 vnchost guacd[105538]: Desktop name "vnchost:2"
Jan 25 04:36:29 vnchost guacd[105538]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:36:29 vnchost guacd[105538]: VNC server default format:
Jan 25 04:36:29 vnchost guacd[105538]:  32 bits per pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  Least significant byte first in each 
pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:36:29 vnchost guacd[105538]: Starting client
Jan 25 04:36:29 vnchost guacd[105538]: client2server supported messages (bit 
flags)
Jan 25 04:36:29 vnchost guacd[105538]: 00: 00ff 0081   -    

Jan 25 04:36:29 vnchost guacd[105538]: 08:  

[jira] [Updated] (GUACAMOLE-719) Guacamole: Multiple simultaneous vnc connections over websocket close each other

2019-01-25 Thread Rui Wang (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rui Wang updated GUACAMOLE-719:
---
Description: 
We are using guacamole to access remote desktop in web-browser. We try to use 
websocket-tunnel for better performance, but if I open two tab in my browser 
connecting to same vnc server with different ports through same guacd server, 
one page get frozen(websocket stop send/receive any messages), the other get 
error like: 776 and disconnected. And we can connect to these two vnc servers 
using vnc-viewer direclty after browser vnc frozen/disconnected.

Seems guacd will abort/kill one after another. It's only happending if we use 
webscoket, using httpeServlet tunnel seems do not have such probelm.

Anyone encounter similar issue? Here are my setup.
 # guacamole-js was used in web side.
 # We use x11vnc, guacd installed with same linux box
 # We developed two endpoints use spring-boot: websocket-tunnel by extending 
GuacamoleWebSocketTunnelEndpoint,http-servlet tunnel by extending 
GuacamoleHTTPTunnelServlet

guacd log here:

 
{code:java}
Jan 25 04:32:58 vnchost guacd[105232]: Protocol "vnc" selected
Jan 25 04:32:58 vnchost guacd[105232]: Connection ID is 
"$7d545e7e-0a29-40e5-a4a3-9964fa07b22b"
Jan 25 04:32:58 vnchost guacd[105232]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:32:58 vnchost guacd[105232]: We have 1 security types to read
Jan 25 04:32:58 vnchost guacd[105232]: 0) Received security type 1
Jan 25 04:32:58 vnchost guacd[105232]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:32:58 vnchost guacd[105232]: Selected Security Scheme 1
Jan 25 04:32:58 vnchost guacd[105232]: No authentication needed
Jan 25 04:32:58 vnchost guacd[105232]: VNC authentication succeeded
Jan 25 04:32:58 vnchost guacd[105232]: Desktop name "vnchost:0"
Jan 25 04:32:58 vnchost guacd[105232]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:32:58 vnchost guacd[105232]: VNC server default format:
Jan 25 04:32:58 vnchost guacd[105232]:  32 bits per pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  Least significant byte first in each 
pixel.
Jan 25 04:32:58 vnchost guacd[105232]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:32:58 vnchost guacd[105232]: Starting client
Jan 25 04:32:58 vnchost guacd[105232]: client2server supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 00ff 0081   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: server2client supported messages (bit 
flags)
Jan 25 04:32:58 vnchost guacd[105232]: 00: 001f 0080   -    

Jan 25 04:32:58 vnchost guacd[105232]: 08:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 10:     -    

Jan 25 04:32:58 vnchost guacd[105232]: 18:     -    
0004
Jan 25 04:32:58 vnchost guacd[105232]: Connected to Server "unknown 
(LibVNCServer 0.9.9)"

Jan 25 04:36:28 vnchost guacd[105538]: Protocol "vnc" selected
Jan 25 04:36:28 vnchost guacd[105538]: Connection ID is 
"$6fd98484-1dd0-4c66-aa04-6c358cd30548"
Jan 25 04:36:29 vnchost guacd[105538]: VNC server supports protocol version 3.8 
(viewer 3.8)
Jan 25 04:36:29 vnchost guacd[105538]: We have 1 security types to read
Jan 25 04:36:29 vnchost guacd[105538]: 0) Received security type 1
Jan 25 04:36:29 vnchost guacd[105538]: Selecting security type 1 (0/1 in the 
list)
Jan 25 04:36:29 vnchost guacd[105538]: Selected Security Scheme 1
Jan 25 04:36:29 vnchost guacd[105538]: No authentication needed
Jan 25 04:36:29 vnchost guacd[105538]: VNC authentication succeeded
Jan 25 04:36:29 vnchost guacd[105538]: Desktop name "vnchost:2"
Jan 25 04:36:29 vnchost guacd[105538]: Connected to VNC server, using protocol 
version 3.8
Jan 25 04:36:29 vnchost guacd[105538]: VNC server default format:
Jan 25 04:36:29 vnchost guacd[105538]:  32 bits per pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  Least significant byte first in each 
pixel.
Jan 25 04:36:29 vnchost guacd[105538]:  TRUE colour: max red 255 green 255 blue 
255, shift red 16 green 8 blue 0
Jan 25 04:36:29 vnchost guacd[105538]: Starting client
Jan 25 04:36:29 vnchost guacd[105538]: client2server supported messages (bit 
flags)
Jan 25 04:36:29 vnchost guacd[105538]: 00: 00ff 0081   -    

Jan 25 04:36:29 vnchost guacd[105538]: 08:     -    

Jan 25 04:36:29 vnchost guacd[105538]: 10:     -    

Jan 25 04:36:29 vnchost guacd[105538]: 18:     -    
0004
Jan 25 04:36:29 vnchost 

[jira] [Commented] (GUACAMOLE-718) Grammatical error in TOTP two-factor authentication manual.

2019-01-25 Thread Michael Jumper (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752771#comment-16752771
 ] 

Michael Jumper commented on GUACAMOLE-718:
--

That line must have been written by a pirate. ;) Minor or not, it's wrong for 
us landlubbers and should be fixed.

> Grammatical error in TOTP two-factor authentication manual.
> ---
>
> Key: GUACAMOLE-718
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-718
> Project: Guacamole
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 1.0.0
>Reporter: Omar Sandoval
>Priority: Trivial
> Fix For: 1.1.0
>
>
> I'm sorry for reporting such a minor thing. Documentation has always been 
> stellar and I'd hate for something like this to slip by.
> In Chapter 9, Enrollment: "... they be required to..." should read "... they 
> _will_ be required to..."
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GUACAMOLE-718) Grammatical error in TOTP two-factor authentication manual.

2019-01-25 Thread Omar Sandoval (JIRA)
Omar Sandoval created GUACAMOLE-718:
---

 Summary: Grammatical error in TOTP two-factor authentication 
manual.
 Key: GUACAMOLE-718
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-718
 Project: Guacamole
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 1.0.0
Reporter: Omar Sandoval
 Fix For: 1.1.0


I'm sorry for reporting such a minor thing. Documentation has always been 
stellar and I'd hate for something like this to slip by.

In Chapter 9, Enrollment: "... they be required to..." should read "... they 
_will_ be required to..."

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GUACAMOLE-717) LDAP authentication fails if search result count exceeds ldap-max-search-result

2019-01-25 Thread Joel Best (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joel Best updated GUACAMOLE-717:

Summary: LDAP authentication fails if search result count exceeds 
ldap-max-search-result  (was: LDAP authentication fails if Sizelimit Exceeded 
exception sent as as search result)

> LDAP authentication fails if search result count exceeds 
> ldap-max-search-result
> ---
>
> Key: GUACAMOLE-717
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-717
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-client
>Affects Versions: 1.0.0
>Reporter: Joel Best
>Priority: Minor
>
> If the search results from an LDAP search exceed ldap-max-search-results, the 
> search will fail and the user will receive an error on login. The logs do not 
> show any indication of what the problem is.
> After troubleshooting, I've determined that the LDAPSearchResults.next() 
> function returns an LDAPException "Sizelimit Exceeded". In 
> ObjectQueryService.search(), this is not handled within the immediate 
> try/catch block so the other valid results are not returned to the calling 
> function. The fix is to also catch LDAPException when catching 
> LDAPReferralException.
> Pull request is incoming.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (GUACAMOLE-717) LDAP authentication fails if Sizelimit Exceeded exception sent as as search result

2019-01-25 Thread Joel Best (JIRA)
Joel Best created GUACAMOLE-717:
---

 Summary: LDAP authentication fails if Sizelimit Exceeded exception 
sent as as search result
 Key: GUACAMOLE-717
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-717
 Project: Guacamole
  Issue Type: Bug
  Components: guacamole-client
Affects Versions: 1.0.0
Reporter: Joel Best


If the search results from an LDAP search exceed ldap-max-search-results, the 
search will fail and the user will receive an error on login. The logs do not 
show any indication of what the problem is.

After troubleshooting, I've determined that the LDAPSearchResults.next() 
function returns an LDAPException "Sizelimit Exceeded". In 
ObjectQueryService.search(), this is not handled within the immediate try/catch 
block so the other valid results are not returned to the calling function. The 
fix is to also catch LDAPException when catching LDAPReferralException.

Pull request is incoming.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GUACAMOLE-312) VNC over SSH

2019-01-25 Thread Michael Jumper (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752519#comment-16752519
 ] 

Michael Jumper commented on GUACAMOLE-312:
--

While historically we haven't been able to progress on this due to libvncclient 
not providing an arbitrary transport, it looks like this may be doable with 
libvncclient after all. Checking the various connection functions implemented 
as part of libvncclient, all seem to simply assign a file descriptor to 
{{client->sock}}. We may be able to have more control over the way connections 
are established if we avoid using {{rfbInitClient()}} and instead invoke the 
various other functions that {{rfbInitClient()}} itself uses to connect.

Assuming the above is a stable approach, libssh2 can be leveraged to provide 
the tunnel, with the actual I/O being handled through read/write calls to 
libssh2 within some thread handling read/write to a socketpair associated with 
libvncclient's {{client->sock}}.

> VNC over SSH
> 
>
> Key: GUACAMOLE-312
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-312
> Project: Guacamole
>  Issue Type: New Feature
>  Components: VNC
>Reporter: Michael Jumper
>Priority: Minor
>
> {panel:bgColor=#EE}
> *The description of this issue was copied from 
> [GUAC-223|https://glyptodon.org/jira/browse/GUAC-223], an issue in the JIRA 
> instance used by the Guacamole project prior to its acceptance into the 
> Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance 
> *have not been copied* and can be found instead at the original issue.
> {panel}
> It would be useful to provide access to VNC over SSH as an option.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (GUACAMOLE-716) Add all LDAP properties to Docker start script

2019-01-25 Thread Nick Couchman (JIRA)


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Couchman resolved GUACAMOLE-716.
-
   Resolution: Implemented
Fix Version/s: 1.1.0

> Add all LDAP properties to Docker start script
> --
>
> Key: GUACAMOLE-716
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-716
> Project: Guacamole
>  Issue Type: Improvement
>  Components: guacamole-docker
>Reporter: Joel Best
>Priority: Trivial
> Fix For: 1.1.0
>
>
> There are still some LDAP properties that are not properly mapped in the 
> start.sh script used for the Docker container:
>  # ldap-group-name-attribute
>  # ldap-dereference-aliases
>  # ldap-max-referral-hops
>  # ldap-operation-timeout
>  # ldap-max-search-results
> I also noticed some of the set_optional_property calls are broken up over 
> multiple lines but will be less than 80 columns if merged to one line. 
> Finally, I plan to re-order the lines in the script to try to match the [LDAP 
> authentication 
> documentation|https://guacamole.apache.org/doc/gug/ldap-auth.html] as closely 
> as possible.
>  
> Pull request will be submitted shortly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GUACAMOLE-715) Permission management based on LDAP groups not working as documented

2019-01-25 Thread Joel Best (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752243#comment-16752243
 ] 

Joel Best commented on GUACAMOLE-715:
-

{quote}The following works:
 # User in both LDAP and database
 # Permission granted to group only in database
 # User added to group only in LDAP{quote}
 

I haven't been able to get this to work. In my testing I found the user had to 
be a member of both the MySQL group and the LDAP group in order for the 
connections to appear.

> Permission management based on LDAP groups not working as documented
> 
>
> Key: GUACAMOLE-715
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-715
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-auth-jdbc-mysql, guacamole-auth-ldap
>Affects Versions: 1.0.0
> Environment: I'm running guacamole in a docker environment using the 
> official base images and a MySQL database. Users are authenticated against an 
> Active Directory server in combination with the MySQL database.
>Reporter: Micha Kohl
>Priority: Major
>
> From the documentation on user groups in 1.0.0 I expected to be able to 
> manage user permissions via LDAP groups like this (using LDAP for 
> authentication and MySQL for configuration management as documented 
> [here|https://guacamole.apache.org/doc/gug/ldap-auth.html#ldap-and-database]):
>  # Create user group in MySQL with the name of a corresponding user group in 
> the LDAP directory 
>  # Create connection in MySQL 
>  # Grant connection permission to the user group created in 1.
>  # LDAP users that are part of the LDAP group (in the directory) are able to 
> log in with their LDAP credentials and access that connection
> This does not work at all (the user does not even see the connection). In my 
> attempt to narrow down the problem and ensure that I'm not just doing it 
> wrong, I tested the following scenarios:
>  # _Having just the LDAP group be mirrored in MySQL by creating an_ 
> _identically named one there_
>  -> Login succeeds, but no associated connections are shown.
>  # _Having both the LDAP group and the user be mirrored in MySQL by creating_ 
> _identically named entities there without manually linking the two (MySQL 
> user is not part of MySQL user group)_
>  -> Login succeeds and guacamole tries to auto-connect to the only available 
> connection/shows all available connections and fails when trying to connect 
> with a permission error.
>  # _Having both the LDAP group and the user be mirrored in MySQL by creating_ 
> _identically named entities there and manually adding the MySQL user to the_ 
> _MySQL group_ _(MySQL user is part of MySQL user group)_
>  -> Connections are established successfully.
> Either there seems to be a big misunderstanding regarding the way the new 
> group system is supposed to work with LDAP, or there's something going wrong 
>  here. It goes without saying that scenario 3 completely eliminates the 
> purpose of relying on existing LDAP groups. Scenario 1 is the configuration I 
> outlined above that would allow managing connections based on LDAP groups 
> without having to create any MySQL users whatsoever. Scenario 2 in 
> combination with similar reports on the mailing list led me to believe that 
> this is either based on a common misconception or there's a bug.
> Side-Note: While it has been suggested that this is already covered by 
> GUACAMOLE-696, I think this could only be said if this turns out to be 
> expected but poorly documented behavior. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GUACAMOLE-699) Multiple fixes and improvements for the german translation

2019-01-25 Thread leetxyz (JIRA)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752120#comment-16752120
 ] 

leetxyz commented on GUACAMOLE-699:
---

[~nick.couch...@yahoo.com] thanks for your input.

As soon as I am ready with the translations, I'll ask my girfriend, who's a 
professional developer, to help me clean my repo up and make a pull request 
according to the guacamole guidelines.

Is there a guideline for testing? On our setup at home I can only test the main 
translation and the auth-totp extension.

> Multiple fixes and improvements for the german translation
> --
>
> Key: GUACAMOLE-699
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-699
> Project: Guacamole
>  Issue Type: Improvement
>  Components: guacamole-client
>Affects Versions: 1.0.0
>Reporter: leetxyz
>Priority: Trivial
> Fix For: 1.1.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Oh hai
> While testing the new 1.0.0 release I found a bunch of typos, missing strings 
> and completely missing translations (e.g. in guacamole-auth-totp and in 
> guacamole-auth-cas) in the german language files.
> Is someone already working on this? If not, do I just need to update 
> guacamole-client/guacamole/src/main/webapp/translations/de.json or are there 
> any other files?
> For the translation of the extension, can I just copy 
> guacamole-client/extensions/guacamole-auth-*/src/main/resources/translations/en.json
>  to de.json and translate it?
> This is my first time trying to get involved in open source, please contact 
> me if I did something wrong in the process.
> best regards



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)