[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=16826574#comment-16826574 ] Michael Jumper commented on GUACAMOLE-249: -- No. It is being worked on, but it is hard to find sufficient time. All, I understand how important this issue is, but please stop asking for updates. When I have more information to report, I will report it. In the meantime, please remain patient and rest assured that it is being worked on. It is blocking the 1.1.0 release and will definitely be finished. > 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: Michael 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 (v7.6.3#76005)
[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=16826556#comment-16826556 ] Abhishek Agarwal commented on GUACAMOLE-249: Hi is there any update on this issue? > 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: Michael 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 (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-715) Permission management based on LDAP groups not working as documented
[ https://issues.apache.org/jira/browse/GUACAMOLE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826460#comment-16826460 ] Nick Couchman commented on GUACAMOLE-715: - [~dchuha]: Okay, Mike's updated query for older MySQL versions has been merged into the staging/1.1.0 branch as well as master, so this should be fixed in the git code. It'll also be fixed in 1.1.0 when that gets released. > 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 >Assignee: Michael Jumper >Priority: Major > Fix For: 1.1.0 > > > 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] [Assigned] (GUACAMOLE-715) Permission management based on LDAP groups not working as documented
[ https://issues.apache.org/jira/browse/GUACAMOLE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman reassigned GUACAMOLE-715: --- Assignee: Michael Jumper (was: Nick Couchman) > 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 >Assignee: Michael Jumper >Priority: Major > Fix For: 1.1.0 > > > 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] [Resolved] (GUACAMOLE-715) Permission management based on LDAP groups not working as documented
[ https://issues.apache.org/jira/browse/GUACAMOLE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-715. - Resolution: Fixed > 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 >Assignee: Michael Jumper >Priority: Major > Fix For: 1.1.0 > > > 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-696) Apply database groups if authenticated user matches database user
[
https://issues.apache.org/jira/browse/GUACAMOLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826434#comment-16826434
]
Nick Couchman commented on GUACAMOLE-696:
-
{quote}
Any ETA for 1.1.0?
{quote}
As soon as we can...
:-)
> Apply database groups if authenticated user matches database user
> -
>
> Key: GUACAMOLE-696
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-696
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-auth-jdbc
>Affects Versions: 1.0.0
>Reporter: matt nelson
>Assignee: Nick Couchman
>Priority: Minor
> Fix For: 1.1.0
>
>
> A user authenticated and logged in with an LDAP account has no access to the
> group permissions assigned to the matching database user.
> if the user logs in using the database user password then the connections do
> appear.
> If the connection permissions are assigned directly to the database user they
> do appear for the LDAP user.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GUACAMOLE-772) Reducing image Docker size for Guacd
[
https://issues.apache.org/jira/browse/GUACAMOLE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman resolved GUACAMOLE-772.
-
Resolution: Implemented
Thanks, [~MathiasM], for the contribution!
> Reducing image Docker size for Guacd
>
>
> Key: GUACAMOLE-772
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-772
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker, guacamole-server
>Reporter: Mathias
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.2.0
>
> Attachments: debian-stable-slim.txt, debian-stable.txt
>
>
> The last Docker image of guacd has a size of around 400 MB. If you use Docker
> image debian/stable-slim as base for guacd, the image size is reduced to a
> total of 330MB. This change (PR #222) is minimal, but has a big benefit. It
> reduces the final Docker image size.
> My comparison is based on the latest public image.
> {code:java}
> $ docker pull guacamole/guacd:1.0.0{code}
>
> REPOSITORY TAG IMAGE ID CREATED
> SIZE
> guacamole/guacd latest 57f6ce568e0d 3 months ago
> 395MB
> intern/guacd latest e562a8exf0x2 2 days
> ago 327MB
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GUACAMOLE-772) Reducing image Docker size for Guacd
[
https://issues.apache.org/jira/browse/GUACAMOLE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman updated GUACAMOLE-772:
Affects Version/s: (was: 1.1.0)
> Reducing image Docker size for Guacd
>
>
> Key: GUACAMOLE-772
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-772
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker, guacamole-server
>Reporter: Mathias
>Priority: Trivial
> Labels: pull-request-available
> Fix For: 1.2.0
>
> Attachments: debian-stable-slim.txt, debian-stable.txt
>
>
> The last Docker image of guacd has a size of around 400 MB. If you use Docker
> image debian/stable-slim as base for guacd, the image size is reduced to a
> total of 330MB. This change (PR #222) is minimal, but has a big benefit. It
> reduces the final Docker image size.
> My comparison is based on the latest public image.
> {code:java}
> $ docker pull guacamole/guacd:1.0.0{code}
>
> REPOSITORY TAG IMAGE ID CREATED
> SIZE
> guacamole/guacd latest 57f6ce568e0d 3 months ago
> 395MB
> intern/guacd latest e562a8exf0x2 2 days
> ago 327MB
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GUACAMOLE-781) Add Czech translation
[ https://issues.apache.org/jira/browse/GUACAMOLE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman resolved GUACAMOLE-781. - Resolution: Implemented Fix Version/s: 1.2.0 Thanks [~Vict0rC], for the contribution! > Add Czech translation > - > > Key: GUACAMOLE-781 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-781 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-client >Reporter: Victor Cleaner >Priority: Minor > Labels: translation > Fix For: 1.2.0 > > Attachments: cz.json > > > Hello, > I just translated the guacamole interface into Czech. If anyone was > interested. > [https://github.com/Vict0rC/guacamole-client-cz] > Based on lates git en.json (v1.1.0) > Victor -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-696) Apply database groups if authenticated user matches database user
[ https://issues.apache.org/jira/browse/GUACAMOLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826068#comment-16826068 ] Craig Bloodworth commented on GUACAMOLE-696: Any ETA for 1.1.0? > Apply database groups if authenticated user matches database user > - > > Key: GUACAMOLE-696 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-696 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc >Affects Versions: 1.0.0 >Reporter: matt nelson >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.1.0 > > > A user authenticated and logged in with an LDAP account has no access to the > group permissions assigned to the matching database user. > if the user logs in using the database user password then the connections do > appear. > If the connection permissions are assigned directly to the database user they > do appear for the LDAP user. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GUACAMOLE-696) Apply database groups if authenticated user matches database user
[ https://issues.apache.org/jira/browse/GUACAMOLE-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826032#comment-16826032 ] Craig Bloodworth commented on GUACAMOLE-696: This also seems to apply for OpenID auth. What part of the openid profile does Guac look for to align with the group name? > Apply database groups if authenticated user matches database user > - > > Key: GUACAMOLE-696 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-696 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-jdbc >Affects Versions: 1.0.0 >Reporter: matt nelson >Assignee: Nick Couchman >Priority: Minor > Fix For: 1.1.0 > > > A user authenticated and logged in with an LDAP account has no access to the > group permissions assigned to the matching database user. > if the user logs in using the database user password then the connections do > appear. > If the connection permissions are assigned directly to the database user they > do appear for the LDAP user. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
