User Specific Settings not used (SSH user/pwd and private key)

User Specific Settings not used (SSH user/pwd and private key)

avatar

I'm running into an annoying problem with user specific settings on a lot of my SSH sessions.

How the sessions are set up:

  • SSH session in some folder
  • Credentials on SSH session left to "Custom" or "None" - doesn't matter, I want everyone to log in with their personal account
  • Personal credentials (username/password or username/private key) in personal vault
  • User specific settings on SSH session overriding credentials, linking to my personal credential entry in my personal vault


When creating a new session this way, this works perfectly fine. I open a session, RDM uses my personal credentials automatically and I'm logged in.

However, after some time, a number of my frequently used SSH sessions stop 'using' the personal credentials. This manifests itself in 2 ways:

  1. SSH sessions with username/password credentials linked just immediately ask for username password through popups - copy/pasting the credentials from my personal entry just works here, so it's not the credentials itself (more on that later)
  2. SSH sessions with private key prompt immediately for a username, but when that username is provided, I'm also logged in - so the private key from the linked personal entry is still used!


So far I found only 1 solution: delete the SSH session completely, and recreate it from scratch as described above (the personal credential entries are not modified during this process!). After that, it works again for some time.

Given the number of SSH sessions we have documented, this solution is not usable in practice.

I'm suspecting some caching or local app data issue, but removing cache folders from the local appdata directory did not resolve this.

We are currently using 2021.1.36.0 and should probably upgrade, but the release notes from this version onwards do not mention any issues relevant to our problem.

Is this some known issue? With a known workaround/solution hopefully? :)

Edit: forgot to mention, but "Open with parameters" > "Open (select credentials)" just experiences the same problem: popups for username/password, popup for username where private key is used but private key is then automatically sent from the personal credential entry

All Comments (2)

avatar

Hello,

Thank you for contacting us on that matter!

Although you are correct that the release notes don't mention any changes to the SSH Shell entry type, my first recommendation would be to try out the latest version, RDM 2021.1.44.0. The SSH Shell entry type is constantly being worked on and improved, although minor changes to it are not always included in the release notes.

Once you have upgraded, if the issue still persists, don't hesitate to let me know and I will see if I am able to replicate this issue on my side to see what we can do about it.

Best regards,


Gabriel Degrandpré

avatar

Hi Gabriel,

I forgot to mention we were using these sessions through RDM Agent on a few jumphosts, and didn't think about this during my troubleshooting. While updating RDM, I realized that RDM on the jumphosts was still a 2020.x version, which had to be upgraded as well.

Now that we're running 2021.1.44.0 on all servers, the issue has disappeared.