meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
applications:connect:windowssql [2023/01/17 20:08] – joetulenkoapplications:connect:windowssql [2023/02/21 21:06] (current) – joetulenko
Line 11: Line 11:
 machines they can make a secure connection without the need to enter a password each time. Thus, the machines they can make a secure connection without the need to enter a password each time. Thus, the
 connection is machine-specific...a key pair installed on your laptop will not also work on your desktop. connection is machine-specific...a key pair installed on your laptop will not also work on your desktop.
 +
 +\\
 +\\
 +----
  
 **Step 1.** Begin the tutorial by navigating over to https://www.heidisql.com/ and download the latest **Step 1.** Begin the tutorial by navigating over to https://www.heidisql.com/ and download the latest
Line 20: Line 24:
  
 {{ :applications:putty_logo.jpg?nolink&400 |}} {{ :applications:putty_logo.jpg?nolink&400 |}}
 +
 +\\
 +\\
 +----
 +
 +**Step 2.** Open PuTTYgen and use the default settings to generate a key. **Make sure the key type is RSA!** This will involve making random
 +movements with your mouse. This should have generated both a ”public” and a ”private” ssh key. The
 +public key should be printed in the box near the top of the window. Copy this and email it to Joe Tulenko (jtulenko@bgc.org) or Greg Balco (balcs@bgc.org). Save the private key in the following directory:
 +
 +
 +{{ :applications:heidi_step2_screenshot.png?nolink&200 |}}
 +
 +
 +This is not a standard directory (i.e., you probably shouldn’t try to make it yourself), but it should
 +either already exist or it might be auto-generated when you use PuTTY.
 +
 +\\
 +\\
 +----
 +
 +**Step 3.** Now that we’ve dealt with SSH keys, open HeidiSQL to connect to the database. The Session
 +Manager window will open, which is where you’ll input the connection parameters. First, make a new
 +Session and give it a sensible name (e.g., ICED remote). Use the template below for the Settings tab (make
 +sure under network type you choose ”MariaDB or MySQL (SSH tunnel); this option is //not// the default):
 +
 +{{ :applications:heidi_step3.1_screenshot.png?nolink&600 |}}
 +
 +Ask Greg (balcs@bgc.org) for the correct IP address to put in the ’Hostname/IP’ field. The User name
 +and Password here are for your ICE-D MySQL account. Talk to Greg (balcs@bgc.org) or Joe (jtulenko@bgc.org) about getting this set up if you haven’t already. In general, users will be using our basic account that has read privileges only. The Databases field can be left empty.
 +
 +Use the following template for the SSH tunnel tab:
 +
 +{{ :applications:heidi_step3.2_screenshot.png?nolink&600 |}}
 +
 +Set the plink.exe location to wherever plink.exe is installed locally on your machine. It will probably
 +be very similar to the example above. Ask Greg or Joe for the correct host name to put in the ’SSH host+port’
 +field. ”Username” here pertains to your username on the SSH gateway machine, which is ”iced.” Leave
 +the Password blank... it is not needed for key pair authentication. Set the Private key file to the location of
 +the private SSH key that you generated using PuTTYgen.
 +
 +\\
 +\\
 +----
 +
 +**Step 4.** Okay, now try opening the connection. In theory, everything should work. Please email either
 +Greg (balcs@bgc.org) or Joe (jtulenko@bgc.org) if you have any issues with the set up. Here is a screen
 +shot of what the samples tab in ICE-D Alpine looks like when successfully connected and viewing the data:
 +
 +{{ :applications:heidi_interface.jpg?nolink |}}
 +
 +Thanks for following along!
 +
 +\\
 +
 +