Bug #73331 Workbench data export from Server 5.1 fails with authentication protocol refused
Submitted: 19 Jul 2014 18:18 Modified: 15 Nov 2014 6:01
Reporter: Greg Thompson Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench Severity:S2 (Serious)
Version: OS:Windows (8.1 64-bit)
Assigned to: CPU Architecture:Any
Tags: authentication protocol, compatibility, Data Export, secure_auth, upgrade issue

[19 Jul 2014 18:18] Greg Thompson
I am attempting to export an old MySQL 5.1.47 database for which I only have read-only access over SSH to a new AWS RDS MySQL database and am running into the "Connection using old (pre-4.1.1) authentication protocol refused" bug reported in #70023 which was closed not actually fixed. Yes, the "Use the old authentication protocol" advanced option in server connections allows me to connect, but as reported in #70023 the Data Export function apparently does not respect the option and still fails.  The error I get is: 

10:24:31 Dumping SpotOn_prod (all tables)
Running: mysqldump.exe --defaults-file="c:\users\greg\appdata\local\temp\tmpspblaw.cnf"  --set-gtid-purged=OFF --max_allowed_packet=1G --host=localhost --protocol=tcp --user=WebSpotOn-RO --port=58785 --default-character-set=utf8 "SpotOn_prod"
mysqldump: Got error: 2049: Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled) when trying to connect

Operation failed with exitcode 2
10:24:33 Export of D:\Users\Greg\Cinespots\Schemas\Dump20140719a.sql has finished with 1 errors

Unfortunately I can not modify the server and only have read-only access over SSH.  What is the workaround to export the schema and all its data so I can import it to a new system?

How to repeat:
Use a recent MySQL Workbench (in my case on Windows 8.1 64-bit) to a older MySQL Server prior to the change in authentication method (in my case MySQL Server 5.1.47 running in an older "redhat-linux-gnu (x86_64)" system) and attempt to do a MySQL Workbench Server->Data Export operation.

Suggested fix:
Looking for a corrected Workbench or workaround (using mysqldump directly?).  Unfortunately Database->Scheme Transfer Wizard doesn't find my TCP/IP over SSH connection to the legacy database and Database->Migration Wizard explicitly says it is not supported over SSH.  While I can use Workbench to see all the data in the legacy database, its too much to manually re-enter in the new MySQL database.  At this point I am stuck (hence the S2 severity).
[25 Jul 2014 18:08] Lukas Siemon
This bug also affects me using Version build 1788

I'd very much appreciate a quick fix.
[10 Sep 2014 21:02] Alfredo Kojima
Try resetting the password for the user in the MySQL server, even if it's to the same password as before.
[16 Nov 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".