[jira] [Updated] (GUACAMOLE-925) Add Russian keyboard support for RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper updated GUACAMOLE-925: -- Component/s: (was: guacamole) RDP > Add Russian keyboard support for RDP > > > Key: GUACAMOLE-925 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-925 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Affects Versions: 1.0.0 >Reporter: Roman Adyev >Priority: Minor > Attachments: SCREEN.jpg > > > Hello, dear support team! > I'm using Unicode layout because Russian layout isn't presented there, but > with Unicode layout I can't send keyboard shortcuts to remote RDP machine > (CTRL + C for example). > If I switch Unicode to English layout in connection settings, I can do > keyboard shortcuts but unfortunately some signs doesn't match when I use RU > layout, for example instead of period sign I got Russian letter "ю". > The keyboard layouts on remote and local machine are identical, that's 100%, > tested many times on different clean windows 10 installs, on work, on VMs, on > friend's PCs, etc. The issue always the same. > As I can see Russian layout isn't presented in Guacamole connection settings > by itself so it would be highly appreciated if you can suggest any workaround > for Russian users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-925) Add Russian keyboard support for RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper updated GUACAMOLE-925: -- Summary: Add Russian keyboard support for RDP (was: Russian layout doesn't work properly) > Add Russian keyboard support for RDP > > > Key: GUACAMOLE-925 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-925 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Roman Adyev >Priority: Minor > Attachments: SCREEN.jpg > > > Hello, dear support team! > I'm using Unicode layout because Russian layout isn't presented there, but > with Unicode layout I can't send keyboard shortcuts to remote RDP machine > (CTRL + C for example). > If I switch Unicode to English layout in connection settings, I can do > keyboard shortcuts but unfortunately some signs doesn't match when I use RU > layout, for example instead of period sign I got Russian letter "ю". > The keyboard layouts on remote and local machine are identical, that's 100%, > tested many times on different clean windows 10 installs, on work, on VMs, on > friend's PCs, etc. The issue always the same. > As I can see Russian layout isn't presented in Guacamole connection settings > by itself so it would be highly appreciated if you can suggest any workaround > for Russian users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-925) Russian layout doesn't work properly
[ https://issues.apache.org/jira/browse/GUACAMOLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper updated GUACAMOLE-925: -- Issue Type: Improvement (was: Bug) > Russian layout doesn't work properly > > > Key: GUACAMOLE-925 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-925 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Roman Adyev >Priority: Minor > Attachments: SCREEN.jpg > > > Hello, dear support team! > I'm using Unicode layout because Russian layout isn't presented there, but > with Unicode layout I can't send keyboard shortcuts to remote RDP machine > (CTRL + C for example). > If I switch Unicode to English layout in connection settings, I can do > keyboard shortcuts but unfortunately some signs doesn't match when I use RU > layout, for example instead of period sign I got Russian letter "ю". > The keyboard layouts on remote and local machine are identical, that's 100%, > tested many times on different clean windows 10 installs, on work, on VMs, on > friend's PCs, etc. The issue always the same. > As I can see Russian layout isn't presented in Guacamole connection settings > by itself so it would be highly appreciated if you can suggest any workaround > for Russian users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-249) Update RDP plugin support to 2.0.0 releases
[ https://issues.apache.org/jira/browse/GUACAMOLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015543#comment-17015543 ] Nick Couchman commented on GUACAMOLE-249: - Way to go [~mjumper]! > Update RDP plugin support to 2.0.0 releases > --- > > Key: GUACAMOLE-249 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-249 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Simone Caronni >Assignee: Mike Jumper >Priority: Critical > Fix For: 1.1.0 > > Attachments: Screenshot_2018-09-01_14-48-56.png > > > The planets have aligned, after 2.5 years FreeRDP has released new snapshots: > https://github.com/FreeRDP/FreeRDP/releases > Thanks, > --Simone -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GUACAMOLE-249) Update RDP plugin support to 2.0.0 releases
[ https://issues.apache.org/jira/browse/GUACAMOLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper resolved GUACAMOLE-249. --- Resolution: Done > Update RDP plugin support to 2.0.0 releases > --- > > Key: GUACAMOLE-249 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-249 > Project: Guacamole > Issue Type: Improvement > Components: RDP >Reporter: Simone Caronni >Assignee: Mike Jumper >Priority: Critical > Fix For: 1.1.0 > > Attachments: Screenshot_2018-09-01_14-48-56.png > > > The planets have aligned, after 2.5 years FreeRDP has released new snapshots: > https://github.com/FreeRDP/FreeRDP/releases > Thanks, > --Simone -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-249) Update RDP plugin support to 2.0.0 releases
[
https://issues.apache.org/jira/browse/GUACAMOLE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015533#comment-17015533
]
Mike Jumper commented on GUACAMOLE-249:
---
*Done!* Thanks [~vnick] and [~jmuehlner] for tackling that beast of a review,
and [~vnick] again for handling what was definitely not a trivial merge back to
{{master}}.
> Update RDP plugin support to 2.0.0 releases
> ---
>
> Key: GUACAMOLE-249
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-249
> Project: Guacamole
> Issue Type: Improvement
> Components: RDP
>Reporter: Simone Caronni
>Assignee: Mike Jumper
>Priority: Critical
> Fix For: 1.1.0
>
> Attachments: Screenshot_2018-09-01_14-48-56.png
>
>
> The planets have aligned, after 2.5 years FreeRDP has released new snapshots:
> https://github.com/FreeRDP/FreeRDP/releases
> Thanks,
> --Simone
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-924) Blank page for ipaddr:8080/guacamole
[
https://issues.apache.org/jira/browse/GUACAMOLE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015280#comment-17015280
]
Mike Jumper commented on GUACAMOLE-924:
---
Please don't open a bug report if you simply have a question about Guacamole.
Use the u...@guacamole.apache.org mailing list instead:
http://guacamole.apache.org/support/#mailing-lists
In 1.0.0 and earlier, an apparently empty page typically indicates that a
failure has occurred so early in the auth process that nothing could render.
The community on the mailing list should be able to help you chase down what is
failing.
> Blank page for ipaddr:8080/guacamole
>
>
> Key: GUACAMOLE-924
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-924
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.0.0
>Reporter: Jean Loce
>Priority: Major
> Attachments: html_response.txt, localhost_access_log.txt
>
>
> Guacamole has been installed via docker image as mentioned in
> [https://www.youtube.com/watch?v=iZB4msyOaUs]
> When using a browser (same result for IE,FF,Chrome) to access guacamole login
> page at [http://ip-addr:8080/guacamole,] the page is just blank.
> However, server returns something that looks valid ('view page source' from
> browser, see html_response.txt as attachment):
> and catalina.out does not report anything error (I was expecting a mysql
> error but no).
> localhost_access_log.txt looks correct too (see attachment).
> tomcat is responding properly at
> [http://ip-addr:8080|http://ip-addr:8080/guacamole,]
> Any idea on what could be wrong and where to look at?
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-924) Blank page for ipaddr:8080/guacamole
[
https://issues.apache.org/jira/browse/GUACAMOLE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Jumper closed GUACAMOLE-924.
-
Resolution: Invalid
> Blank page for ipaddr:8080/guacamole
>
>
> Key: GUACAMOLE-924
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-924
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
>Affects Versions: 1.0.0
>Reporter: Jean Loce
>Priority: Major
> Attachments: html_response.txt, localhost_access_log.txt
>
>
> Guacamole has been installed via docker image as mentioned in
> [https://www.youtube.com/watch?v=iZB4msyOaUs]
> When using a browser (same result for IE,FF,Chrome) to access guacamole login
> page at [http://ip-addr:8080/guacamole,] the page is just blank.
> However, server returns something that looks valid ('view page source' from
> browser, see html_response.txt as attachment):
> and catalina.out does not report anything error (I was expecting a mysql
> error but no).
> localhost_access_log.txt looks correct too (see attachment).
> tomcat is responding properly at
> [http://ip-addr:8080|http://ip-addr:8080/guacamole,]
> Any idea on what could be wrong and where to look at?
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GUACAMOLE-924) Blank page for ipaddr:8080/guacamole
Jean Lusetti created GUACAMOLE-924:
--
Summary: Blank page for ipaddr:8080/guacamole
Key: GUACAMOLE-924
URL: https://issues.apache.org/jira/browse/GUACAMOLE-924
Project: Guacamole
Issue Type: Bug
Components: guacamole
Affects Versions: 1.0.0
Reporter: Jean Lusetti
Attachments: html_response.txt, localhost_access_log.txt
Guacamole has been installed via docker image as mentioned in
[https://www.youtube.com/watch?v=iZB4msyOaUs]
When using a browser (same result for IE,FF,Chrome) to access guacamole login
page at [http://ip-addr:8080/guacamole,] the page is just blank.
However, server returns something that looks valid ('view page source' from
browser, see html_response.txt as attachment):
and catalina.out does not report anything error (I was expecting a mysql error
but no).
localhost_access_log.txt looks correct too (see attachment).
tomcat is responding properly at
[http://ip-addr:8080|http://ip-addr:8080/guacamole,]
Any idea on what could be wrong and where to look at?
Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-923) NLA without predefined user credentials
[ https://issues.apache.org/jira/browse/GUACAMOLE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper closed GUACAMOLE-923. - Resolution: Duplicate > NLA without predefined user credentials > --- > > Key: GUACAMOLE-923 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-923 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Dinoop >Priority: Major > > We've more than 100 servers and about 100 users who all are connecting to > these servers via RDP. We need to keep the server RDP settings as NLA enabled. > Are there any options in Guacamole to connect to these servers without > predefining the user credentials and NLA enabled? > This is an urgent requirement. Please advice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-923) NLA without predefined user credentials
[ https://issues.apache.org/jira/browse/GUACAMOLE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014968#comment-17014968 ] Mike Jumper commented on GUACAMOLE-923: --- Your best option currently would be to integrate Guacamole with an authentication backend shared by your RDP servers (such as Active Directory via LDAP) leverage parameter tokens to dynamically pass through the users' credentials without storing them: https://guacamole.apache.org/doc/gug/configuring-guacamole.html#parameter-tokens If you have any questions on the above, please use the u...@guacamole.apache.org mailing list rather than JIRA: http://guacamole.apache.org/support/#mailing-lists Outside of that, the remaining option would be to prompt for those credentials. Credential prompting is not currently implemented, but already has a JIRA issue: GUACAMOLE-221. > NLA without predefined user credentials > --- > > Key: GUACAMOLE-923 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-923 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Affects Versions: 1.0.0 >Reporter: Dinoop >Priority: Major > > We've more than 100 servers and about 100 users who all are connecting to > these servers via RDP. We need to keep the server RDP settings as NLA enabled. > Are there any options in Guacamole to connect to these servers without > predefining the user credentials and NLA enabled? > This is an urgent requirement. Please advice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GUACAMOLE-923) NLA without predefined user credentials
Dinoop created GUACAMOLE-923: Summary: NLA without predefined user credentials Key: GUACAMOLE-923 URL: https://issues.apache.org/jira/browse/GUACAMOLE-923 Project: Guacamole Issue Type: Improvement Components: guacamole Affects Versions: 1.0.0 Reporter: Dinoop We've more than 100 servers and about 100 users who all are connecting to these servers via RDP. We need to keep the server RDP settings as NLA enabled. Are there any options in Guacamole to connect to these servers without predefining the user credentials and NLA enabled? This is an urgent requirement. Please advice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
