Connecting via SSH, create an ODBC connection and using the SSH connection.
A client of mine kept their PostgreSQL database locked away behind an SSH connection. As in most situations, convincing the IT department to change security rules for one dashboard was not a hill I was willing to climb. Instead, I used some old techniques I’d used to connect to my home servers back when I had such a thing.
I use SSH rarely now so I make use of a Chrome extension called Secure Shell for the occasional SSH connection. For this blog post, I’m going to be using the Chrome extension, but the same technique will work with PuTTY or any other SSH tool.
In the image above, a connection was established to the PostgreSQL database through the SSH client. The connection was then routed through a port on the local machine.
Once the SSH connection was set up, I created a System DSN that connected to the PostgreSQL database by routing through the local port. (The numbers below correspond to the numbers in the image above.)
Once the connection was set up, using it was relatively simple.
Once the connection string was created, selecting tables was the same as connecting to any other database. The only annoyance is having to connect via the SSH client before reloads.
This article originally appeared on the Unconventional QlikView blog.