[jira] [Commented] (GUACAMOLE-1085) Consider migrating web application from AngularJS
[ https://issues.apache.org/jira/browse/GUACAMOLE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258503#comment-17258503 ] Mark Nolan commented on GUACAMOLE-1085: --- You can build Angular applications using a Maven plugin (e.g. frontend plugin), though I have no experience with that in practice. It would probably work for any npm/yarn compatible framework. > Consider migrating web application from AngularJS > - > > Key: GUACAMOLE-1085 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1085 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Alfred Egger >Priority: Major > > [AngularJS is in an LTS period until June 30, > 2021|https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c]. > Unless resurrected as a community-driven project, it will be cease being > maintained after that date. Assuming no such project surfaces, we should look > into migrate the web application to another framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1085) Consider migrating web application from AngularJS
[ https://issues.apache.org/jira/browse/GUACAMOLE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258491#comment-17258491 ] James Muehlner commented on GUACAMOLE-1085: --- It looks like LTS support for AngularJS has been [extended to December 31st, 2020|https://docs.angularjs.org/misc/version-support-status], but in any case we are now within 1 year of the end of AngularJS. I agree with [~manolan] that migrating to Angular would be a major undertaking, requiring at least a partial rewrite of the entire application. It does look like there are some tools provided to help upgrade AngularJS apps to Angular, so this is probably the easiest/smoothest path to upgrading. As far as alternative frameworks, I have the most experience working with react, which I _believe_ is now eligible for use in ASF projects [after being re-licensed under MIT|https://engineering.fb.com/2017/09/22/web/relicensing-react-jest-flow-and-immutable-js/]. It looks like upgrading to either React or Angular would likely also require changing the way the build works. We many need to buy at least partially into the whole NPM/Babel/Webpack/Browserify ecosystem. I have no experience with Vue. I'd also be happy to work on migrating to whatever framework comes next. It looks like Angular is probably the leading candidate at the moment. > Consider migrating web application from AngularJS > - > > Key: GUACAMOLE-1085 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1085 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Alfred Egger >Priority: Major > > [AngularJS is in an LTS period until June 30, > 2021|https://blog.angular.io/stable-angularjs-and-long-term-support-7e077635ee9c]. > Unless resurrected as a community-driven project, it will be cease being > maintained after that date. Assuming no such project surfaces, we should look > into migrate the web application to another framework. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GUACAMOLE-1252) NAS-IP-Adress should be configurable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-1252: Assignee: Nick Couchman > NAS-IP-Adress should be configurable > > > Key: GUACAMOLE-1252 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, guacamole-auth-radius >Affects Versions: 1.3.0 >Reporter: Michael Böhm >Assignee: Nick Couchman >Priority: Minor > > This change introduced the functionality to read the ip address from the OS > and write it to the NAS IP address of the RADIUS protocol. > However, this is not a proper solution when Guacamole runs in Docker as in > this case the virtual internal IP address is used. > As discussed in the mailing-list, I propose to make it configurable from > where the NAS IP address should be fetched, either automatically from the OS > or manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1252) NAS-IP-Adress should be configurable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1252: - Component/s: Documentation > NAS-IP-Adress should be configurable > > > Key: GUACAMOLE-1252 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, guacamole-auth-radius >Affects Versions: 1.3.0 >Reporter: Michael Böhm >Priority: Minor > > This change introduced the functionality to read the ip address from the OS > and write it to the NAS IP address of the RADIUS protocol. > However, this is not a proper solution when Guacamole runs in Docker as in > this case the virtual internal IP address is used. > As discussed in the mailing-list, I propose to make it configurable from > where the NAS IP address should be fetched, either automatically from the OS > or manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-1252) NAS-IP-Adress should be configurable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258233#comment-17258233 ] Nick Couchman commented on GUACAMOLE-1252: -- Pull requests have been opened for this change: https://github.com/apache/guacamole-client/pull/586 https://github.com/apache/guacamole-manual/pull/157 > NAS-IP-Adress should be configurable > > > Key: GUACAMOLE-1252 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 > Project: Guacamole > Issue Type: New Feature > Components: Documentation, guacamole-auth-radius >Affects Versions: 1.3.0 >Reporter: Michael Böhm >Priority: Minor > > This change introduced the functionality to read the ip address from the OS > and write it to the NAS IP address of the RADIUS protocol. > However, this is not a proper solution when Guacamole runs in Docker as in > this case the virtual internal IP address is used. > As discussed in the mailing-list, I propose to make it configurable from > where the NAS IP address should be fetched, either automatically from the OS > or manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1252) NAS-IP-Adress should be configurable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-1252: - Priority: Minor (was: Critical) > NAS-IP-Adress should be configurable > > > Key: GUACAMOLE-1252 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-radius >Affects Versions: 1.3.0 >Reporter: Michael Böhm >Priority: Minor > > This change introduced the functionality to read the ip address from the OS > and write it to the NAS IP address of the RADIUS protocol. > However, this is not a proper solution when Guacamole runs in Docker as in > this case the virtual internal IP address is used. > As discussed in the mailing-list, I propose to make it configurable from > where the NAS IP address should be fetched, either automatically from the OS > or manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GUACAMOLE-1251) OpenID connect and #
[ https://issues.apache.org/jira/browse/GUACAMOLE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman closed GUACAMOLE-1251. Resolution: Duplicate I responded to your e-mail on the mailing list. This almost certainly has nothing to do with the "#" in the Guacamole URL, and is probably related to GUACAMOLE-560, which deals with certain OpenID IdPs requiring the state parameter, despite the fact that the specification doesn't require it. > OpenID connect and # > > > Key: GUACAMOLE-1251 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1251 > Project: Guacamole > Issue Type: Bug > Components: guacamole-auth-openid >Affects Versions: 1.3.0 > Environment: native >Reporter: Alexander >Priority: Major > Attachments: 12345.zip > > > Hello! > I need help with OpenID > My project: > > I need to provide users with access to remote desktops (RDP) via browser. > But I want to use standalone server like Gluu (the one that we are currently > using) or even better - Keycloak, so we won't have to use Guacamole for > authorization. I tested both of them, the result looks quite the same. > This is how I tested: I manually created a local account 'user1' on Gluu/KC > (Is there a necessary to have an account with the same login and password on > Guacamole? Or a new user will be created?) > I'm using Guacamole 1.2. I installed the extension as recommended here: > https://guacamole.apache.org/doc/gug/openid-auth.html > Also I found out there that 'implicit flow' is used. > Minimal parameters that must be specified: > > openid-authorization-endpoint: > openid-jwks-endpoint: > openid-issuer: > openid-client-id: > openid-redirect-uri: > > Ok, then i going to edit guacamole.properties > __ > if I use Gluu > openid-authorization-endpoint: https://gluu.homelab/oxauth/restv1/authorize > openid-jwks-endpoint: https://gluu.homelab/oxauth/restv1/jwks > openid-issuer: https://gluu.homelab > openid-client-id: 64f2088d-d9f8-4742-906b-497219446e9f > openid-redirect-uri http://guac.homelab > > on Gluu side > https://i.imgur.com/VSW17o7.png > OPENID CONNECT CLIENTS DETAILS > -- > - Name: guac > - Client ID: 64f2088d-d9f8-4742-906b-497219446e9f > - Subject Type: pairwise > - ClientSecret: XXX > - Application Type: web > - Persist Client Authorizations: false > - Pre-Authorization: false > - Authentication method for the Token Endpoint: client_secret_jwt > - Logout Session Required: false > - Include Claims In Id Token: false > - Disabled: false > - Login Redirect URIs: [https://guac.homelab] > - Grant types: [implicit, authorization_code, client_credentials, > refresh_token] > - Response types: [token, code, id_token] > __ > if I use Keycloak > openid-authorization-endpoint: > http://kc.homelab/auth/realms/homelab/protocol/openid-connect/auth > openid-jwks-endpoint: > http://kc.homelab/auth/realms/homelab/protocol/openid-connect/certs > openid-issuer: http://kc.homelab/auth/realms/homelab > openid-client-id: guacamole > openid-redirect-uri: https://guac.homelab > > on Keycloak side > https://i.imgur.com/EBti48h.png > set client id - guacamole > enable "Implicit Flow" > set Base url https://guac.homelab > __ > > Now setup is over. I open browser and try to go to https://guac.homelab > I enter login and password and get into the loop as it's shown in the videos: > https://youtu.be/OjwhCB9pjQw > https://youtu.be/1dbNnVKp6PA > > Guacamole logs are attached below or available here: > https://dropmefiles.com/d2D95 > > Can you tell me what am I doing wrong? > My colleagues suggest that the problem could be in the character #, which is > used by Guacamole. Could it be the reason of the issue? > > P.S. > I tried to connect other products via openid to KC/Gluu (open source crm) and > everything works just fine. > I found similar issue here: > https://www.reddit.com/r/homelab/comments/bukjbe/help_with_gluu_open_id_connect_to_guacamole/epdtj8k/ > And the video that looks like mine: > https://i.imgur.com/MwWppLs.mp4 > > Thank you in advance! > Best regards -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GUACAMOLE-925) Add Russian keyboard support for RDP
[ https://issues.apache.org/jira/browse/GUACAMOLE-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258171#comment-17258171 ] NFisher commented on GUACAMOLE-925: --- [~mjumper] It looks like we're treading water ;) I have 2 layouts and 2 languages installed on local Windows 10 and on remote Windows 2016 - ENG (English United States with US keyboard) and RUS (Russian with Russian keyboard). On both systems I have [Ctrl]+[Shift] combination to switch between input languages and no combination to switch keyboard layouts explicitly (in terms of standard Windows "Change key sequence" form). !image-2021-01-04-14-42-50-393.png! Now let's go back to the start post. 1. If I set Unicode layout - both Russian and English keyboards work ok but [Ctrl]+ combinations don't. Like [Ctrl]+[F], [Ctrl]+[C], etc... 2. When I added Russian keymap to guacamole-server and guacamole-client, Russian keyboard worked ok along with [Ctrl]+ sequences. But English layout was broken for some keys and [Ctrl]-sequences as well. That's all I know. Since all systems are now Unicode-compatible, I think there's no need to add more layouts explicitly. Just [Ctrl]-sequences should be fixed for Unicode-layout. I guess the trouble is that the [Ctrl]-sequences are treated literally when should be treated via scan-codes. Also keep in mind that the bug is 1 year (and 3 releases) old ;) > 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, apache_guacamole_Russian_layouts.txt, > image-2021-01-04-14-42-50-393.png, ru_ru_qwerty.keymap > > > 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 ] NFisher updated GUACAMOLE-925: -- Attachment: image-2021-01-04-14-42-50-393.png > 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, apache_guacamole_Russian_layouts.txt, > image-2021-01-04-14-42-50-393.png, ru_ru_qwerty.keymap > > > 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-1252) NAS-IP-Adress should be configurable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Böhm updated GUACAMOLE-1252: Description: This change introduced the functionality to read the ip address from the OS and write it to the NAS IP address of the RADIUS protocol. However, this is not a proper solution when Guacamole runs in Docker as in this case the virtual internal IP address is used. As discussed in the mailing-list, I propose to make it configurable from where the NAS IP address should be fetched, either automatically from the OS or manually from a config parameter (or not at all). was: This [change|https://issues.apache.org/jira/browse/GUACAMOLE-1001] introduced the functionality to read the ip address from the OS and write it to the NAS IP address of the RADIUS protocol. However, this is not a proper solution when Guacamole runs in Docker as in this case the virtual internal IP address is used. As discussed in the mailing-list, I propose to make it configurable how the NAS IP address should be created, either automatically from the OS or manually from a config parameter (or not at all). > NAS-IP-Adress should be configurable > > > Key: GUACAMOLE-1252 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-radius >Affects Versions: 1.3.0 >Reporter: Michael Böhm >Priority: Critical > > This change introduced the functionality to read the ip address from the OS > and write it to the NAS IP address of the RADIUS protocol. > However, this is not a proper solution when Guacamole runs in Docker as in > this case the virtual internal IP address is used. > As discussed in the mailing-list, I propose to make it configurable from > where the NAS IP address should be fetched, either automatically from the OS > or manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-1252) NAS-IP-Adress should be configurable
[ https://issues.apache.org/jira/browse/GUACAMOLE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Böhm updated GUACAMOLE-1252: Description: This [change|https://issues.apache.org/jira/browse/GUACAMOLE-1001] introduced the functionality to read the ip address from the OS and write it to the NAS IP address of the RADIUS protocol. However, this is not a proper solution when Guacamole runs in Docker as in this case the virtual internal IP address is used. As discussed in the mailing-list, I propose to make it configurable how the NAS IP address should be created, either automatically from the OS or manually from a config parameter (or not at all). was: This change introduced the functionality to read the ip address from the OS and write it to the NAS IP address of the RADIUS protocol. However, this is not a proper solution when Guacamole runs in Docker as in this case the virtual internal IP address is used. As discussed in the mailing-list, I propose to make it configurable how the NAS IP address should be created, either automatically from the OS or manually from a config parameter (or not at all). > NAS-IP-Adress should be configurable > > > Key: GUACAMOLE-1252 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 > Project: Guacamole > Issue Type: New Feature > Components: guacamole-auth-radius >Affects Versions: 1.3.0 >Reporter: Michael Böhm >Priority: Critical > > This [change|https://issues.apache.org/jira/browse/GUACAMOLE-1001] introduced > the functionality to read the ip address from the OS and write it to the NAS > IP address of the RADIUS protocol. > However, this is not a proper solution when Guacamole runs in Docker as in > this case the virtual internal IP address is used. > As discussed in the mailing-list, I propose to make it configurable how the > NAS IP address should be created, either automatically from the OS or > manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GUACAMOLE-1252) NAS-IP-Adress should be configurable
Michael Böhm created GUACAMOLE-1252: --- Summary: NAS-IP-Adress should be configurable Key: GUACAMOLE-1252 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1252 Project: Guacamole Issue Type: New Feature Components: guacamole-auth-radius Affects Versions: 1.3.0 Reporter: Michael Böhm This change introduced the functionality to read the ip address from the OS and write it to the NAS IP address of the RADIUS protocol. However, this is not a proper solution when Guacamole runs in Docker as in this case the virtual internal IP address is used. As discussed in the mailing-list, I propose to make it configurable how the NAS IP address should be created, either automatically from the OS or manually from a config parameter (or not at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
