Bug #6118 ODBC 3.51 driver is getting client authentication error

• Submitted: 15 Oct 2004 17:35
• Modified: 19 Apr 2005 18:03
• Reporter: Kevin Westwoood
• Status: Not a Bug
• Category: Connector / ODBC
• Severity: S1 (Critical)
• Version: 3.51
• OS: Windows (Windows XP)
• CPU Architecture: Any

[15 Oct 2004 17:35] Kevin Westwoood

Description:
The ODBC 3.51 driver seems to be using the old password authentication hashing algorithm.  I am getting the "Client does not support authentication protocol" error when trying to Test the datasource/Connect using the ODBC 3.51 driver.

How to repeat:
install mySQL 4.1.6-gamma and startup instance
install ODBC 3.51 driver.  Open Microsoft ODBC Data Source Administrator.  Create MySQL Data source using the 3.51 driver.  Configure the data source correctly and click the Test Data Source button.  You get the authentication error.

Suggested fix:
It seems that the driver is using the old password scheme.

[19 Oct 2004 2:30] MySQL Verification Team

Verified on XP.

[20 Oct 2004 9:44] Sinisa Jovanovic

Is there any solution for ODBC 3.51 and mySQL 4.1 gama on XP ?

[20 Oct 2004 16:07] Kevin Westwoood

There is a solution, you have to change your users to logon using the old password scheme.  This is described in section A.2.3 of the mySQL Manual.  I actually did not attempt this.  I installed the MySQL 4.0 server and clients instead.  It is not an issue there.

[20 Oct 2004 16:17] MySQL Verification Team

HI!

3.51 is not built to work with MySQL 4.1.

ODBC 3.53 will work with 4.1, but it is still in development and it will take few months
before it is released.

[19 Apr 2005 14:12] Edward Soniat

The 3.51 readme says it support 4.1 and we have used it successfully

[19 Apr 2005 18:03] MySQL Verification Team

When I wrote my remark, 3.51.11 was not out yet.