Scenario: * ThinLinc 4.8.0-5431.r32425 (Jenkins, pre-release) * SLE 12 SP2 with Workstation Extension 1. Start a new ThinLinc session as root with the standard Gnome profile. 2. Wait until the screensaver locks the screen 3. Try to unlock the screensaver. You will now get a warning under the password field that says that "System administrator is not allowed to remote login", and the field resets itself after 2-3 seconds. Entering the password before the form resets does not allow you to log in. If the system has a restriction of this kind, we should ensure that we're bound by it when creating a ThinLinc session as well. In other words, the system administrator shouldn't be allowed to create a ThinLinc session with this setup.
See: https://bugzilla.opensuse.org/show_bug.cgi?id=995062 The Suse "solution" was to document that GDM is required. Apparently, if you do not run GDM, the screensaver will never lock. This might also be a problem, but likely much less severe than the original one. I do not think that we should obey GDM policies. The system might use something else, such as lightdm. See also: https://bugzilla.redhat.com/show_bug.cgi?id=960149
We'll need to check the exact criteria for when this triggers. Is it only root or is it everyone in the "wheel" group (or equivalent)?
There is a display manager sysconfig used to disable remote root logins on SUSE. See param DISPLAYMANAGER_ROOT_LOGIN_REMOTE in file /etc/sysconfig/displaymanager which is default set to "no". Changing this value to "yes" and restart gdm will allow root to unlock screensaver. Also tested that a user who is member of wheel group is not affected, even if polkit rules is added to add wheel group users as admins. polkit.addAdminRule(function(action, subject) { return ["unix-group:wheel"]; });