Skip jump host server connection when running from jump host itself
Skip jump host server connection when running from jump host itself
0 vote
Hi all
Feature request: when a connection is configured to use a jump host, it should automatically skip the jumphost if it is already running from the jumphost itself.
We're using RDM jump host to connect to remote, firewall protected environments quite often.
We have quite a big problem that a jump host within a jump host is not working/supported in RDM, which is a pity of course, but we need it for a number of connections that are not directly reachable from our admin workstations.. Sometimes we have to jump 2 or even up to 3 servers before reaching the target.
So the solution for us is, to first RDP / RDM into our 1st jump host server, from there 'interactively' start Devolutions RDM again (connected to the same shared datasource) and start a jump host session that will jump 1 step further.
Now comes my problem/hickup: we've configured the folder for the target connections to use a jump host. clicking the entry will make RDM first try to RDP to the local server itself (which FAILS). Of course we can work around by right -click the entry, choose Open with Parameters - select 'Open via Jump...' select 'Direct (no jump)' but that is just a little too cumbersome.
Using the jump host from a remote machine works as expected. (connects to jump host, then to target) but has the disadvantage it can't go deeper than that.
Finally a last solution I've tried: on the jump host, configure the folder properties : 'Edit - Local specific setting' where I can specify credentials and jump host; configure the jump host for 'no jump' . However, this doesn't work. (bug?)
when I configure the same setting on the connection entry itself ('Edit - Local specific setting') - jump host: no jump it works. The connection entry has 'jump host' configured as 'inherited' so it is not inheriting this local specific setting, unfortunately.
wow, long story... Bottom line is: it would be ideal if we can configure a jump host on a folder or connection entry, and when using that connection, it should auto-detect if it is already on that jump host, and skip this part.
Regards, Ben
All Comments (3)
Ben,
Thank you for the feedback.
Feature request: when a connection is configured to use a jump host, it should automatically skip the jumphost if it is already running from the jumphost itself.
Not sure how we could detect that we are on the jumphost already. I need to think about this one.
We have quite a big problem that a jump host within a jump host is not working/supported in RDM, which is a pity of course, but we need it for a number of connections that are not directly reachable from our admin workstations.. Sometimes we have to jump 2 or even up to 3 servers before reaching the target.
Multiple jumps would be nice, it's always been on my mind, maybe one day we will implement it.
Now comes my problem/hickup: we've configured the folder for the target connections to use a jump host. clicking the entry will make RDM first try to RDP to the local server itself (which FAILS). Of course we can work around by right -click the entry, choose Open with Parameters - select 'Open via Jump...' select 'Direct (no jump)' but that is just a little too cumbersome.
You should have "Direct (no jump)" button on the dashboard.
Finally a last solution I've tried: on the jump host, configure the folder properties : 'Edit - Local specific setting' where I can specify credentials and jump host; configure the jump host for 'no jump' . However, this doesn't work. (bug?)
Looks like a bug we will investigate.
Best regards,
Stéfane Lavergne
Hello,
Sorry about the delay, but I had a question regarding your following issue:
Finally a last solution I've tried: on the jump host, configure the folder properties : 'Edit - Local specific setting' where I can specify credentials and jump host; configure the jump host for 'no jump' . However, this doesn't work. (bug?)
I tried to reproduce the issue in our environment and I noticed that the "local specific setting", in the case of Jump, only applies if you restart RDM, or if you do a full refresh (Ctrl+F5) of the datasource. Otherwise, it seems to work properly. Can you confirm? FYI I've been testing on our latest version, 2020.2.19.0.
We'll work on figuring out why this requires a refresh at the moment, it's not intended behavior.
Regards,
Hubert Mireault
We found why the refresh is currently required, and it will be fixed with the release of RDM 2020.3.
Regards,
Hubert Mireault