Hi Rolandas,
there were issues with these more exotic sssd providers, that's why they were removed from the image as mentioned in the changelog. The simplest ways to re-enable are:
1, Via a root-fs customization assigned to the nodes concerned that re-adds the removed files (see /usr/share/doc/qlustar-module-core-noble-amd64-14.1/core.contents.changelog.gz). With this method you have to make sure to update the bianries, whenever a new sssd release appears.
2. Install the sssd-common package in the chroot assigned to the nodes concerned and run 'systemctl enable sssd-ssh; systemctl restart sssd' in an rc.boot script like you described.
To make this more convenient, we will re-add the needed service binaries to the core image module in the next security release and just leave the services disabled.
Best,
Roland
On 9/29/26 09:54, Rolandas Naujikas via Qlustar General wrote:
Hi,
Workaround:
Put files from head node (if arch and OS version is the same)
/usr/libexec/sssd/sssd_ssh and /usr/libexec/sssd/sssd_check_socket_activated_responders to /etc/qlustar/images/<qlustar image for login nodes>/copy/usr/libexec/sssd/
and systemctl enable sssd-ssh; systemctl restart sssd in /etc/qlustar/common/rc.boot/login script for login nodes only.
Another way is to enable via Qluman-GUI via sssd.conf, but then it could cause other problems in Lustre or computing nodes.
Regards Rolandas
On 2026-09-29 09:43, Rolandas Naujikas wrote:
Hi,
After latest upgrade ssh keys based authentication stopped to work. We are using sss_ssh_authorizedkeys command in sshd_config
AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys AuthorizedKeysCommandUser nobody
But nor in ssh nor in command line it doesn't work anymore. For e.g.
sss_ssh_authorizedkeys USERNAME Error looking up public keys
Users are still visible via sssd and alternative authentication (for e.g. Kerberos) works.
Regards Rolandas