MaybeLexter opened a new issue, #9413:
URL: https://github.com/apache/hop/issues/9413
### What would you like to happen?
#### Current Behavior
Apache Hop supports SSH tunneling for relational database connections, but
the current SSH Tunnel configuration only allows users to specify a single SSH
server.
There is no option to configure multiple SSH jump hosts in a connection
chain.
#### Problem
In some enterprise networks, accessing a database requires connecting
through multiple SSH jump hosts.
For example:
`Apache Hop → Jump Host 1 → Jump Host 2 → Target SSH Server → Database`
Each SSH server may use different credentials or authentication methods,
such as a private key for one host and a password for another.
Currently, this requires external SSH tunnels, scripts, or additional
network configurations, making database connections harder to manage and deploy.
#### Proposed Enhancement
I would like Apache Hop to support multiple SSH jump hosts in the existing
SSH Tunnel configuration, similar to DBeaver.
The configuration should allow users to:
1. Add, remove, and reorder SSH jump hosts.
2. Configure each host independently, including:
- Hostname or IP address.
- SSH port.
- Username.
- Authentication method (password or private key).
- Private key file and passphrase, when applicable.
3. Establish SSH connections sequentially in the configured order.
4. Automatically forward database traffic through the SSH chain.
5. Save the jump host settings as part of the database connection metadata.
The SSH Tunnel tab could include an ordered list of jump hosts, similar to
DBeaver's "Jump servers" section.
Existing single-hop SSH connections should continue to work without
requiring any configuration changes.
#### Expected Behavior
When multiple jump hosts are configured, Apache Hop should connect to each
SSH server in the specified order and establish the final tunnel to the
database.
The JDBC driver should then connect through the resulting local port
forwarding, preserving the existing behavior, including support for manual JDBC
URLs using `${sshTunnel.localPort}`.
#### Use Case
Consider an Oracle database hosted in an isolated network that cannot be
accessed directly from the machine running Apache Hop.
Access requires:
- **Jump Host 1:** Accessible from Apache Hop, using private key
authentication.
- **Jump Host 2:** Accessible through Jump Host 1, using password
authentication.
- **Target SSH Server:** Accessible through the jump chain and able to reach
the Oracle database.
- **Oracle Database:** Accessible only from the internal network.
DBeaver already supports this type of configuration through its SSH Jump
Servers feature.
Adding similar functionality to Apache Hop would allow users to configure
and execute pipelines without maintaining external SSH tunnels.
#### Benefits
- Support for database connections that require multiple SSH jump hosts.
- Less dependency on external SSH scripts and manual tunnel configurations.
- Easier management and deployment across different environments.
- Support for different authentication methods at each SSH hop.
- Centralized SSH configuration within Apache Hop database connections.
**Apache Hop — Current SSH Tunnel Configuration**
<img width="1492" height="424" alt="Image"
src="https://github.com/user-attachments/assets/f75dad20-2f36-48eb-8719-758a90260f22"
/>
**DBeaver — Multiple SSH Jump Hosts Configuration**
<img width="729" height="534" alt="Image"
src="https://github.com/user-attachments/assets/1026b704-25ef-4998-886b-7e526f18c354"
/>
#### Reference
DBeaver provides a similar feature through its SSH Jump Servers
configuration:
https://dbeaver.com/docs/dbeaver/SSH-Configuration/#configuring-jump-servers
### Issue Priority
Priority: 3
### Issue Component
Component: Database
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]