RDM upgrade broke SSH key login
Good morning,
Typically, we use RDM for connecting to all our Linux servers using pre-made/shared SSH keys. This is the way my team has used it for years.
We hadn't upgraded our RDM client (2023.3.39.0) for a good while, but recently found time to upgrade it to the latest, and further upgraded again today as there was another release. We're now on 2024-2.21.0 64-bit. For this upgrade we had to install .NET 8.
So, onto the problem....
Since the upgrade, RDM no longer appears to attempt to send the SSH keys to our RDM connection target. It just seems to try to log in via password (which the server would expectedly reject) and fail.
If I check the RDM host profile (based on a template) I see
Credentials : "My personal credentials"
I seem to remember, or have a feeling, that this should be set to "My personal SSK key" (or words to that effect), but if I click the drop-down to change it back, there exists no option to change it.
Am I looking at the right thing here? Surely SSH key login hasn't removed from RDM!? If I go to File... My account settings... My personal SSH key... I can see my configuration, with the SSH key either copy/pasted or I can point to the path of the SSH key file. So it looks like RDM still supports SSH keys in principle, but where am I missing the piece where I restore the use of this login type in all our connections.
As a sanity check, I fired up standard PuTTY client, pointed it to my SSH key, and boom, it worked first time, straight onto one of our servers. So I know this is a problem in RDM.
Please tell me SSH key login hasn't been removed from RDM!? This would be a deal breaker for my team.
Kind regards,
Elliot
All Comments (4)
So I thought I was onto something by changing the connection profile's connection "Credentials" setting from "My personal credentials" to "My privileged account". As upon drilling into this option it appears to ultimately point to "My personal SSH key".
However, despite thoroughly checking the config of this SSH key screen, RDM still just appears to try to login to our target using standard username. "My personal SSH key" is pre-configured with my login name, so I am expecting RDM to simply send the username with the SSH key and successfully login, but it still appears to not even send the username :|
server_auth_1.png
Edit_SSH_key-Login_name.png
Edit_SSH_key-General.png
Edit_Host.png
I have just started up my laptop with an old RDM installed (2023.3.39) and connecting to the same server I was testing throughout this exercise via this old client successfully connects, so it does look like something has broke in the newer version of RDM :(
So, through unrelenting trial-and-error, I have (hopefully) found the changes required to restore previous functionality.
Apparently, I need to manually edit each and every one of our server connections/profiles, changing two things:
1) Credentials : "My personal credentials" to Credentials : "My privileged account"
2) Tick the checkbox "Use credentials from template".
To be honest, I've been messing with settings all morning, so it's possible there were some other config changes which contributed to the fix, but the above was definitely the piece finally got it working.
Hopefully this may be of use to others who encounter the same issues following an upgrade.
Kind regards,
Hello Elliot,
Thank you for contacting us about the SSH key login issue.
I’m glad to hear that you found a solution.
I will close this forum thread, as your solution appears to be effective, and I’ll make a note of it.
Best regards,
Carl Marien