[jira] [Updated] (GUACAMOLE-872) Guacamole Rest API Documentation
[ https://issues.apache.org/jira/browse/GUACAMOLE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-872: - Fix Version/s: (was: 1.1.0) > Guacamole Rest API Documentation > - > > Key: GUACAMOLE-872 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-872 > Project: Guacamole > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.0.0 > Environment: XML >Reporter: samir chahine >Priority: Minor > Labels: pull-request-available > Attachments: Screen Shot 2019-09-05 at 4.14.41 pm.png > > Original Estimate: 0h > Remaining Estimate: 0h > > I have created a new page for information regarding the access of the > Guacamole API through a Rest Framework. > In my search for a well documented list of api calls I was never able to find > one, rather I broke apart the pre-built API to discover the endpoints > necessary to make these functionalities possible. > > This is the pull request: > [https://github.com/apache/guacamole-manual/pull/123] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (GUACAMOLE-699) Multiple fixes and improvements for the german translation
[ https://issues.apache.org/jira/browse/GUACAMOLE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper resolved GUACAMOLE-699. -- Resolution: Done > 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 (v8.3.2#803003)
[jira] [Commented] (GUACAMOLE-877) Add support for Okta MFA
[ https://issues.apache.org/jira/browse/GUACAMOLE-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926235#comment-16926235 ] Nick Couchman commented on GUACAMOLE-877: - Sounds like a good plan. What protocol(s) does Okta use for this? REST API? RADIUS? > 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.2#803003)
[jira] [Updated] (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 updated GUACAMOLE-877: Priority: Minor (was: Major) > 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.2#803003)
[jira] [Created] (GUACAMOLE-877) Add support for Okta MFA
Triet Le created GUACAMOLE-877: -- Summary: 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 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.2#803003)
[jira] [Commented] (GUACAMOLE-876) RDP "reconnect" resizing breaks Drive Mapping
[ https://issues.apache.org/jira/browse/GUACAMOLE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925530#comment-16925530 ] Richard Lancaster commented on GUACAMOLE-876: - > interrupting the file transfer with the "reconnect" method - I don't think >this is a bug in Guacamole, nor do I think it's an issue that is resolvable Is it feasible to know when a file is in transit? We could disable resizing (likely just ignoring the client's `size` command) whilst this is happening. I haven't reported this (as I haven't found a FreeRDP ca1cec6 build to be very stable, ended up removing it in hopes for FreeRDP 2 support soon), but a dynamic resize during a file transfer has other issues (segfault, broken drive map). Typically the entire RDP session just hung when I started the the file transfer (this didn't happen with strace attached, so it sounds like a race condition to me). Is this work reporting separately? > RDP "reconnect" resizing breaks Drive Mapping > - > > Key: GUACAMOLE-876 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-876 > Project: Guacamole > Issue Type: Bug > Components: guacd >Affects Versions: 1.1.0 >Reporter: Richard Lancaster >Priority: Minor > Attachments: guacd.log, guacd_resize_file_trasfer.mp4 > > > In the attached video you can see resizing a connection with the resize > method "reconnect", will halt any current file transfers (leaving corrupted > files) and sporadically leave the drive map unconnected for the new session. > > The associated guacd logs associated with the video are attached. > > Running: > * Web frontend - 1.0.0 (the official guacamole/guacamole docker image) > * Guacd - staging/1.1.0 (381ff1a4214e06803f0f587f1ed97cf7e54853e7) (Built > against ubuntu 18.04's libfreerdb-dev) > > Let me know if there is any more info you need. -- This message was sent by Atlassian Jira (v8.3.2#803003)
