Jump Server feature request

[Molin-L]

Is your feature request related to a problem? Please describe.

No, it works totally fine.

Describe the solution you'd like

The reason that I still use termius is that it provides very smooth jump server for connection.

I want to replace termius with wave. But currently it's not easy to connect a host behind a jump server.

I am not sure if this feature is want you expect wave could do. But it looks like a nice-to-have one.

[esimkowitz]

This is definitely something we want to support, though I don't have any hard dates yet. I have some questions to help us figure out the proper design for a feature like this:

• Would you plan on using this to connect to the same jump server from multiple clients? If so, which clients would you expect to use?
• Would you want to be able to connect to both a jump server and other locally-configured server connections or would you manage all your server connections through the jump server?
• Would you want the jump server to store and persist your user settings for Wave or would you want those to stay local to your machine?
• What sort of access controls (OAuth, username/password, SSH key, etc.) do you expect for the jump server?
• Would you want multiple users to have access to this jump server?
• Would you want us to host this jump server or do you want it to be self-hosted?
• Do you think a jump server should be limited to a single workspace/tab or do you want to see all jump server and non-jump server connections in the same view?

[Molin-L]

@esimkowitz Thx for ur prompt response. And I wish my answer would help:

1. Yes, I use ssh and sftp at the same time to connect to jump server.
2. I will connect to those hosts behind a jump server and those directly connected server at the same time. So locally configuration is better for me. Or is it possible to add these servers to a group, and make this as a group configuration?
3. Actually I don't really know, since some setting is invalid when the network environment change. But it's nice to have.
4. In the most time I use SSH key, but some servers have to use OAuth, and they are mostly in my work environment, which means I cannot make change on access controls. So I have to switch to another ssh client if it's not supported.
5. No, jump servers are providing a pathway to access other servers, so multi-user doesn't mean a lot to me.
6. In my scenarios, the jump server is the entrance of our internal network, so it's self-hosted. But it makes sense to have u to host a jump server if these server doesn't have public ip address.
7. I want to see all servers in the same view. Since in my daily use, I don't really care about how these servers connected, seamless connection may be good for me.

I hope my personal preference would help u. Thanks again