[
https://issues.apache.org/jira/browse/GUACAMOLE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264414#comment-17264414
]
Nick Couchman commented on GUACAMOLE-1257:
------------------------------------------
With a simpler test, I'm not able to reproduce this behavior. I'm using
Guacamole with PostgreSQL, and I did the following:
- Set "postgresql-absolute-max-connections: 1" in guacamole.properties and
reload the web application.
- Log in with guacadmin and start a connection.
- Log in with a test account and try to start another connection. I receive an
error that the connection is in use and concurrent connections are not allowed.
- Drop the connection from guacadmin and try with the test account, which
succeeds.
- While test account is running the connection, try to start with guacadmin,
and I receive the concurrent error message.
- Log out of guacadmin and log with the test account (so now both browsers have
the same test account logged in).
- Start the connection in one browser, then attempted to start it in another
browser, and receive error.
- Drop the connection from one browser, start it in the other browser.
- Attempt to start a second instance of the connection, receive the concurrent
error.
Essentially it appears to me that at least the
"postgresql-absolute-max-connections" parameter works as expected. I have not
tried the various default ones, yet.
> 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)