MySQL Bugs: #52048: Server instance manager cannot update SSH certificate file once it is entered

Bug #52048	Server instance manager cannot update SSH certificate file once it is entered
Submitted:	14 Mar 2010 16:15	Modified:	10 Nov 2010 14:30
Reporter:	stu thompson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.16	OS:	MacOS (10.6)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When setting up a new instance to connect via SSH with an SSH certificate file, the location of the certificate file is not actually saved.  This was also present in earlier version, ~5.2.11

How to repeat:
- Server Administration >> New Server Instance
- Remote Host, with IP address
- Set the database connection values
  - Connection Method: Standard TCP/IP over SSH
  - SSH Host Name = server IP
  - SSH Key File = **incorrect file path**
  - Continue
- Get error message, Go Back
- Set SSH Key File to correct path
- Continue

Note that the error message still shows the old path.  The new path seems to not have been updated internally.

sorry for the long delay (i missed to change the status when i initially checked the report).

do you type or paste the keyname to the field or use the browse-button to select a keyfile? i wasnt able to reproduce your problem here.
thanks in advance

Sorry for my long delay!  I was busy getting married overseas :P  

I typed the keyname to the field becauase navigating to it was not possible.  (I keep the certs in a folder called ~/.certs/, which does not show in finder.

Stu

Could not reproduce using WB 5.2.21 using Mac OS X 10.6.
Using an incorrect file, then using correct files (which has public SSH key) works.

I was to fast!

Got indeed in to problems as described.

When you specify the wrong location of a key-file, you get the password prompt. When you cancel or make it error, and you try to specify the correct location of your key-file, behavior is odd. It then asks for the password of the MySQL root user instead of the SSH user.

Verified using WorkBench 5.2.16 on Mac OS X 10.6

I meant: Verified using 5.2.21-RC

Workaround is to exit the dialog and try again, or don't make a mistake :)

Fixed already in release.

confirmed in repository

An entry has been added to the 5.2.30 changelog:

When a new instance was created to connect via SSH with an SSH certificate file, the location of the certificate file was not saved.