[update] Securely Manage Remote PostgreSQL Servers with pgAdmin on Mac #7150
Conversation
…c OS X updated the guide to include instructions using the inbuilt SSH tunneling in pgAdmin 4
✅ Deploy Preview for nostalgic-ptolemy-b01ab8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for nostalgic-ptolemy-b01ab8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| - **Tinnel port**: `22` . This is the default SSH port. | ||
| - **Username**: Your SSH username for the Linode instance. | ||
| - **Authentication**: Choose `Identity file` if you are using an SSH key, or `Password` for password-based authentication. | ||
| - **Identity file**: If you are using an SSH key, browse and select the private key file. |
There was a problem hiding this comment.
@Rajakavitha1 is this accurate? I asks to select a "private key". Is this actually referring to a user's pubic key they would need to provide?
There was a problem hiding this comment.
Hi @jddocs I checked the official documentation and this is what it reads: https://www.pgadmin.org/docs/pgadmin4/development/server_dialog.html
*Specify the type of authentication that will be used when connecting to the SSH host in the Authentication field:
Select the Password option to specify that pgAdmin will use a password for authentication to the SSH host. This is the default.
Select the Identity file to specify that pgAdmin will use a private key file when connecting.*
The users public key is uploaded when the hardening the SSH access even before PostgreSQL is installed on Linode. My understanding is that it is the private key that is used to securely establish an SSH connection to the server. The server verifies this key against the public key stored in the ~/.ssh/authorized_keys file on the Linode instance.
updated the guide to include instructions using the inbuilt SSH tunneling in pgAdmin 4
Fixes: #3153