Hi,
This is a follow-up to my previous thread User Specific Settings not used (SSH user/pwd and private key) (devolutions.net), where an upgrade of both my 'central' RDM application and the RDM application on the jumphost to 2021.1.44.0 solved the issue of connections not using user-specific settings.
I'm now running into a similar problem using the "Open (select credentials)" feature. So summarized:
When I open the session normally, the jumphost session launches, RDM gets started within the jumphost, and I'm logged in with my personal credentials. All fine and well.
However, I have a second set of private key credentials, which give me elevated access to the host in question. So I right-click the session, select "Open (select credentials)", pick my elevated account and try to log in that way. The result: RDM on the jumphost opens a second SSH session, but logs me in with my normal user.
If I change the user-specific credentials on the session to my elevated credentials, RDM keeps logging me in with my normal user.
Only when I completely close RDM on the jumphost, change the user-specific settings on the session, and relaunch the session (and thus RDM on the jumphost), then I can login with my elevated account. Ofcourse, now I cannot do a login with my normal account until I repeat this process :)
In the Connections.log file on the jumphost I do see a line like this when I select explicit credentials:
[9-9-2021 10:38:30] Information - 'private key entry name': Used by 'session name' [Session] (Private)
I tried playing around a bit with cache settings and clearing, but found nothing so far. Any insight?
Hello,
Would you be able to send a quick recording of the issue, showing how your session(s) are configured and the behavior, using the link that I sent you in Private Messages?
Best Regards,
Etienne Lord
Hello,
Thank you for the recording, I can indeed see the issue clearly. I will investigate on that.
Best Regards,
Etienne Lord
Hello,
A ticket is open with the engineering department in order to have a look at the issue, will keep you updated!
Best Regards,
Etienne Lord
Hi Etienne,
Thanks, looking forward to engineering's findings :)
Frederic
Hello,
We are currently working on resolving this issue, and I'd like to know if you updated to a 2021.2.x version, and if you are still having problems ?
If you are still on 2021.1.44, would you mind updating to a more recent version and try again ? We are unable to reproduce this issue at the moment.
Regards
Jonathan Del Signore