Bug 8333 - Deleted user accounts may occupy ThinLinc licenses
Summary: Deleted user accounts may occupy ThinLinc licenses
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-16 12:25 CEST by Martin Östlund
Modified: 2024-04-16 13:56 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Martin Östlund cendio 2024-04-16 12:25:14 CEST
If a user has been removed from the system while still having a ThinLinc session running, it will be difficult to remove the session from the session store.

For example, trying to terminate a session with tlctl, where user 'test1' has been removed from the system:

[root@lab-97 ~]# tlctl session terminate --user=test1
Refreshing session information...

Terminating:
USER   DISPLAY  AGENT    
=========================
test1  10       127.0.0.1

Summary:
  Terminate 1 session(s)

Is this ok? [y/N]: y
tlctl: error: failed to terminate session 10 for test1 on VSM Agent 127.0.0.1
tlctl: error: failed to terminate 1 session(s). Check /var/log/vsmserver.log for more information

vsmserver.log:
>2024-04-16 12:21:00 INFO vsmserver.session: User with uid 0 requested termination of 127.0.0.1:10
>2024-04-16 12:21:00 WARNING vsmserver.session: kill_session: User with uid 1001 does not exist

Likewise, from tlwebadm when trying to terminate, it will report:

>Failed to terminate session 10 for test1 on agent 127.0.0.1. Check >/var/log/vsmserver.log for explanation.
Comment 2 Martin Östlund cendio 2024-04-16 13:33:44 CEST
In the above scenario, it is sufficient to kill the user's tl-session manually, and vsmserver will take notice and remove the session metadata from its session store.

Note You need to log in before you can comment on or make changes to this bug.