Bug 8598 - Validate SLES 16.0 Beta
Summary: Validate SLES 16.0 Beta
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Server OS (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.19.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-05 14:55 CEST by Linn
Modified: 2025-06-18 16:22 CEST (History)
3 users (show)

See Also:
Acceptance Criteria:


Attachments

Description Linn cendio 2025-06-05 14:55:22 CEST
Test that the following works:

* Basic function (Graphics, Mouse, Keyboard) 
* Network transport
* Server installation (and setup)
* Session startup
* Sound redirection
 - Input (mic)
 - Output
* Drive redirection  
* Printer redirection  
* Web integration    
* OpenGL  
* Nearest printer
 - Access control 
* Restricted shell (thinlinc-login)
* Restricting SSH Daemon Port Forwarding ("PermitOpen")
* Smart card redirection
* Authentication
 - Interactive 
 - Password
 - OTP
 - Public key 
 - Smart card
 - Kerberos
Comment 1 Linn cendio 2025-06-10 13:52:33 CEST
When testing, we noticed three problems preventing a working session. These are the workarounds we used:

1. The SELinux module in tlsetup caused a traceback and failed to install the necessary package. This was resolved through installing package "selinux-policy-devel" manually.

2. tlsetup failed to start the services due to not finding the PAM-files we use. We look for either /usr/lib/pam.d/sshd or /usr/lib/pam.d/remote. The following command solved it:
> sudo cp /usr/lib/pam.d/sshd /etc/pam.d/
3. No X11-desktop can be installed by default. With a gnome wayland desktop installed on the system, add the desktop-file as described in 
https://community.thinlinc.com/t/no-executable-profiles-found-on-rhel-10-almalinux-10-and-rocky-10/1553
Comment 2 Linn cendio 2025-06-11 12:51:05 CEST
Tested the following with server build 4097:

✅ Authentication
 ☑️ Interactive 
   ✅ Password
   ❓ OTP [1]
 ✅ Public key 
 ✅ Smart card
 ✅ Kerberos

[1]: OTP is done via the Google Authenticator package, which on SLES seems to be named "google-authenticator-libpam". This package is not currently available for SLES 16, but is under development according to the linked page below. We should revisit OTP once this package is available.
https://software.opensuse.org/package/google-authenticator-libpam
Comment 3 Madeleine cendio 2025-06-11 17:13:29 CEST
Tested Server installation+setup with server build 4097. I encountered bug 8480 when testing the graphical installer and bug 8212 when starting new sessions.

I noticed some warnings in /var/log/vsmagent, not sure if this is new for SLE 16, but I’ve reported it in bug 8606.
Comment 4 Hannes cendio 2025-06-12 14:14:06 CEST
Tested the following with server build 4097:

✅ Printer redirection 
✅ Nearest printer 
 ✅ Access-control
✅ Web integration
✅ OpenGL
Comment 5 Samuel Mannehed cendio 2025-06-16 22:42:19 CEST
(In reply to Linn from comment #1)
> 2. tlsetup failed to start the services due to not finding the PAM-files we
> use. We look for either /usr/lib/pam.d/sshd or /usr/lib/pam.d/remote. The
> following command solved it:
> > sudo cp /usr/lib/pam.d/sshd /etc/pam.d/

Note this PR regarding this:

https://github.com/cendio/ansible-role-thinlinc-server/pull/48
Comment 6 Linn cendio 2025-06-17 14:38:37 CEST
Tested the following with server build 4097:

✅ Smart card redirection
Comment 7 Linn cendio 2025-06-17 15:40:54 CEST
Tested authentication via OTP by downloading package "google-authenticator-libpam" from SLES 15, and managed to get things working.

✅ Interactive 
  ✅ Password
  ✅ OTP
Comment 8 Hannes cendio 2025-06-17 16:03:27 CEST
Tested the following with server build 4097:

✅ Sound redirection 
✅ Drive redirection 
✅ Restricted shell
✅ Basic function
✅ Restricting SSH Daemon Port Forwarding
✅ Network transport
✅ Custom session startup
Comment 9 Linn cendio 2025-06-18 09:07:37 CEST
With that, all tests have been performed. With the workarounds mentioned in comment 1 in place, things seem to be working well. Closing.

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