[
https://issues.apache.org/jira/browse/GUACAMOLE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264420#comment-17264420
]
Nick Couchman commented on GUACAMOLE-1257:
------------------------------------------
Did more testing and confirmed that things appear, to me, to be working as
expected:
- Set "postgresql-default-max-connections: 1" and
"postgresql-default-max-connections-per-user: 1" in guacamole.properties
- Tested with various combinations of the same user logging in from multiple
browsers and multiple users logging in.
In all of the tests that I did, the system behaves as expected - blocks
connections when the limits are reached, and allows the connections up to that
point. I'm not seeing behavior that indicates that there's anything broken,
here. The only difference that I can see is that you're using the MySQL module
and I'm using the Postgres module. I'm also testing with a later version (1.3.0
instead of 1.2.0). Maybe you could try Guacamole Client 1.3.0 and see if you're
able to reproduce the issue?
> Unable to limit no of concurrent users
> --------------------------------------
>
> Key: GUACAMOLE-1257
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1257
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 1.2.0
> Environment: Debian 10, GCP
> Reporter: Reuben Rodrigues
> Priority: Minor
>
> *How to reproduce?*
> 1. Set the following parameters with values of one:
> * {{mysql-absolute-max-connections}}
> * {{mysql-default-max-connections}}
> * {{mysql-default-max-group-connections}}
> * {{mysql-default-max-connections-per-user}}
> * {{mysql-default-max-group-connections-per-user}}
> 2. When the same user tries to access another instance of Guacamole from
> another tab he is allowed
>
> *Expected Behavior*
> Only one user should be able to connect at a given time
>
> Am I missing anything in the settings here? Any help would be appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
