Feature Request: Native SSH Tunneling for Database Connectors

Feature Request: Integrated SSH Tunneling (Bastion Host) in DB Connector Nodes

I am requesting that the Database Connector nodes include a built-in configuration tab for SSH Tunneling.

Currently, there is no intuitive way to connect the SSH Connector node to the MySQL Connector node. The nodes do not share compatible input/output ports by default, meaning I cannot physically wire the SSH connection into the database driver.

Because these nodes cannot be connected, I am forced to leave KNIME and set up a manual SSH tunnel via my operating system’s terminal (ssh -L ...). This breaks the workflow’s self-containment and makes it impossible to share with non-technical users.

Proposed Solution: Add a dedicated “SSH / Tunneling” tab inside the configuration dialog of the Database Connector nodes (similar to DBeaver or Tableau).

This tab should allow me to:

  1. Input the Jump Server (Bastion) Host, User, and Key directly inside the DB node.

  2. Eliminate the need to use a separate “SSH Connector” node entirely.

  3. Automatically handle the local port forwarding in the background when the node executes.

Business Value: This is standard functionality in almost all SQL clients (DBeaver, Sqlectron, Workbench). Adding this to KNIME would prevent users from having to rely on external CLI workarounds just to connect to secure enterprise databases.

1 Like

Hello @PanteleyShmele1,

this is a long standing feature request. See this topic and vote:

Br,
Ivan

2 Likes