Primary informations
Cluster: baobab (yggdrasil and bamboo work fine with the same key)
Description
My Outsider account authenticates successfully via SSH public key
on both Yggdrasil and Bamboo, but the same key is rejected on
Baobab login1.
On Yggdrasil, sss_ssh_authorizedkeys <username> correctly returns
my registered ed25519 key. On Baobab, the key is rejected (ssh -vvv
shows type 51 after offering the key), SSH falls back to
keyboard-interactive (password prompt), and the connection is
eventually closed.
I suspect this may be related to the dual identity issue mentioned
in the March 2025 changelog (OpenOnDemand authentication fix
affecting users with Collaborator/Student dual identities). My
account has both an Outsider identity and a student identity, both
visible in the sss_ssh_authorizedkeys output on Yggdrasil.
Could you check whether sss_ssh_authorizedkeys returns my key on
login1.baobab, and whether my account is correctly provisioned on
that cluster?
Thank you