I understood. By the way, is there any way to disable c from connecting in the same situation?
2021年9月14日(火) 19:37 Nick Couchman <vn...@apache.org>: > On Tue, Sep 14, 2021 at 6:26 AM takuya morita <mrttky521...@gmail.com> > wrote: > >> Hi I am Takuya. >> Thank you for the other day. >> >> I was studying Guacamole again today. >> Is "Session Affinity" working properly? >> >> I tried the following steps. >> 1.I have a connection group has two connections. >> 2.I set connection group as follows. >> -Maximum number of connections: 2 >> -Maximum number of connections per user: 1 >> -Enable session affinity: on >> 3.A has logged in Guacamole and connect to that connection group. >> 4.B has logged in Guacamole and connect to same connection group A has. >> 5.C tried to login Guacamole but he failed. >> 6.B logout from Guacamole. >> 7.C tried to login Guacamole again and he succeeded. >> >> If "Session Affinity" is working well, C will fail, right? >> >> > No, Session Affinity does not mean that Connection 2 will be "locked" to > User B. It means that Guacamole will attempt to give the same connection to > the same user, if that connection is available. If the connection is > unavailable, the user will be routed to a different connection within the > group, and if there is only one connection left, then it will be given to > the first user who needs/requests it (User C in your example). Furthermore, > as stated in the manual, session affinity only lasts until the user logs > out from Guacamole - that is, it is tied to the user's session, not the > user: > > > http://guacamole.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-schema-connection-groups > > -Nick > >>
