Bug #53673 Login failure when connecting via STD TCP/IP over SSH on Mac
Submitted: 15 May 2010 17:48 Modified: 23 Jun 2010 11:04
Reporter: Frederick Richart Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.21.RC OS:MacOS (10.5.8)
Assigned to: CPU Architecture:Any
Tags: keychain login

[15 May 2010 17:48] Frederick Richart
Description:
Get login failure when trying to make a DB connection via STD TCP/IP over SSH.  I cannot find a workaround and this only occurs on Mac OS X.  Do not experience problem on Ubuntu Linux with same version of MySQLWorkbench and exact same configuration.

Failure message is

Failed to Connect to MySQL at 127.0.0.1:3306 through SSH tunnel at myhost.com:2222 with user root

Incorrect database name '
<myDBPassword>
<myDBPassword>
'

How to repeat:
Setup a DB connection to a remote system using STD/ TCP/IP over SSH
SSH Hostname myserver.com:2222 (servers uses port 2222 for SSH)
SSH Username root
Use SSH Key file for SSH tunnel (no SSH Password)
MySQL Hostname 127.0.0.1
MySQL Server Port 3306
Username root

Advanced Tab 
Use compression protocol checked 
others not checked
[17 May 2010 12:19] Susanne Ebrecht
Which database name did you use?
[18 May 2010 12:45] Frederick Richart
When you ask which database name, do you mean Defalult Schema?  If so, it is blank - I don't want any particular schema selected.
[18 May 2010 12:58] Frederick Richart
Setting a default schema didn't change the failure other than it also appearing in the error message when I Test Connection.

Incorrect database name 'cphulkd
<myDBPassword>
<myDBPassword>
'
[28 May 2010 11:15] Geert Vanderkelen
Can not repeat this particular problem using WorkBench 5.2.21 on MacOS X 10.6.
Maybe 10.5 specific?
[28 May 2010 13:05] Frederick Richart
I installed 5.2.21.RC on my macbook running 10.6.3 and also cannot repeat the problem on this system.  So it appears that for my environment only 10.5 is impacted
[23 Jun 2010 11:04] Susanne Ebrecht
This is a duplicate of bug #53623

The bug already is fixed since Workbench 5.2.22.

Please try actual version Workbench 5.2.24 RC