SSH Shell Session - Link SSH Gateways from vault

Hi,

In this context, SSH Gateways is a setting of the SSH Shell entry. What would you like it to link to in the Vault? Other SSH entries? A SSH Gateway entry (it does not exist, but we have a RDP Gateway for RDP)?

Best regards,

Yes, would like to link to other ssh entries.
Same for all other ssh entry types that have a ssh gateway/jumphost

Hi,

How do you want this to work exactly? At the moment, if you configure multiple gateways in that screen, the SSH session will "chain" through all of the configured gateways. Do you just want us to fetch the linked SSH entries settings from session, but otherwise, work exactly like it is now. This would be relatively easy to implement.

Or, do you expect us to "chain" through the SSH gateways of the SSH entry configured as a gateway? e.g. SSH1 as one gateway configured, SSH2, and SSH2 as one gateway configured, SS3. The session would then go SSH1 -> SSH2 -> SSH3. This would be a lot more tricky and wouldn't really fit in the current workflow.

Best regards,

Ideally it would use a dynamic lookup for the chaining method.

Workable would be something like:

• add link to existing host and a button to retrieve the listed chains on that host (eg precalculate the chain). That button can later be used to "refresh" the chain. No need to manually add other hosts in that case.

Eg:

• on SSH3: no gateway defined
• on SSH2: link to SSH3, "calculate chain" -> only SSH3 appears
• on SSH1: link to SSH2, "calculate chain" -> looks at pre-calculated chain of SSH2: SSH2 -> SSH3
• SSH4 gets added, no gateway defined
• SSH3 changes, gateway linked to SSH4, "calculate" -> SSH4
  • Either SSH1/2 stays the same, and need a manual "recalculate"
  • or calculate knows SSH2 links to SSH3 and needs refresh (in turn that SSH1 links to SSH2 and also needs refresh)

(in case of auto recalculate, the ok/save button can trigger that as well)

In my case, I have several entries using the same chains, so only having to link to the last host of the chain is a big +++

Hmmm... In that case, wouldn't just adding a button "Fill with entry" and just fill the Gateway list that actually exists works? We would lose the references to the entry (so if any entry in the chain changes in the future, the change would need to be reapplied).

So:

1) SSH4 contains no gateway.
2) In SSH3, we click "Fill with entry" and chose SSH4. The host/port/credentials/key of SSH4 is now configured in the gateways of SSH3.
3) In SSH2, we click "Fill with entry" and chose SSH3. The host/port/credentials/key of SSH3 AND SSH4 (from the SSH3 gateway list) are filled in the gateways of SSH2.
4) In SSH1, we click "Fill with entry" and chose SSH2. The host/port/credentials/key of SSH2, SSH3 and SSH4 are filled in the gateways of SSH1

Of course, if no references are preserved, any change to SSH4, SSH3 or SSH2 will require a regenerate in SSH1 (same for SSH2 and SSH3 with their own gateways).

If we are to go into saving references of the entries, a recursive lookout become necessary, and then, might as well do this lookout on launch instead of a recalculate button.

Best regards,