Ah, thanks Nick, originally I read the question differently. Upon
re-reading I think I understood the detail incorrectly.
Indeed if the first user *deliberately* logged out, then the second user
comes along and can log into the original Win session that's a Win issue
alright.
On 7/05/2020 9:20 a.m., Nick Couchman wrote:
On Wed, May 6, 2020 at 4:58 PM ivanmarcus
<[email protected]> wrote:
If I understand your problem correctly; the issue is that a user
doesn't log off properly, another user coming along can then take
over the original session if the original session hasn't
automatically timed out?
If a user hasn't correctly logged off then Guacamole has no way of
knowing if there is simply a 'glitch' in internet traffic,
someone's taken a quick break, or whether the user has indeed
gone. Because of this there is a specific session timeout value,
the default is 60 minutes.
It gets a little more complicated than that. From the original e-mail...
"we have the challenge, that our users use common service accounts to
login into a windows server with rdp"
So, the users are sharing Windows accounts, which is why one use can
close/disconnect the Guacamole session and another user can come back
and log in to that disconnected session and get the same session that
the previous user had.
Again, I don't think this is a challenge with Guacamole, nor is it
something that Guacamole can resolve - this sounds to me more like a
Windows RDP session management issue.
-Nick
