ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MariaDB client

[nmggithub]

I am in college, and my University has given us each a MariaDB database login for a database course we have. PHPMyAdmin can connect, as well as the Linux mariadb package, and also the Node.js mariadb package. This extension does not work and gives the above error. I have tried the known fix and it did not solve it.

[nmggithub]

Update: it appears my user is: "IDENTIFIED VIA pam". Not sure if this is what is causing the auth failure.

[mtxr]

Witch MariaDB version are you using? Also, can you try to connect using 'xprotocol' as described in https://vscode-sqltools.mteixeira.dev/connections/mysql#know-errors-and-how-to-fix

…

On May 23 2019, at 8:38 pm, Noah Gregory ***@***.***> wrote: Update: it appears my user is: "IDENTIFIED VIA pam". Not sure if this is what is causing the auth failure. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub (#246?email_source=notifications&email_token=AAFMX2KC6OTEPFRY2F5IQUTPW4TH5A5CNFSM4HPLBVNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDYTZY#issuecomment-495421927), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAFMX2KUGT77BPE4CU2SXGLPW4TH5ANCNFSM4HPLBVNA).

[mtxr]

@nmggithub did you get it working?

I'll close this issue, but please, re-open if you still face some problems.

[nmggithub]

It is MariaDB v10.1.32. And, per my last message, "I have tried the known fix and it did not solve it." So, yes I did try the xprotocol fix. It did not solve it.

[nmggithub]

After looking into it some more, it appears the issue is with the mysql Node.js package. I just installed it locally and am receiving the same error. I do not receive the error when using the mariadb Node.js package. There is an open issue over at the repository for the mysql package and I informed them of this. I can look through the source code of both packages and see if I can find what the issue is.

[mtxr]

Which port are you using? Did you try adding a 0 in the end? Eg: 3306 -> 33060

MySQL/MariaDB xprotocol usually runs in another port.

Would you mind sharing your connection settings? blurring username, password and server of course.

I'll try to reproduce this here during the weekend.

[mtxr]

After looking into it some more, it appears the issue is with the mysql Node.js package. I just installed it locally and am receiving the same error. I do not receive the error when using the mariadb Node.js package. There is an open issue over at the repository for the mysql package and I informed them of this. I can look through the source code of both packages and see if I can find what the issue is.

That's awesome! If you want, you can submit a PR implementing a dialect for MariaDB only. Then we could detach the support from mysql to mariadb.

Take a look at #219 , let me know what you think

[nmggithub]

After looking into it some more, it appears the issue is with the mysql Node.js package. I just installed it locally and am receiving the same error. I do not receive the error when using the mariadb Node.js package. There is an open issue over at the repository for the mysql package and I informed them of this. I can look through the source code of both packages and see if I can find what the issue is.

That's awesome! If you want, you can submit a PR implementing a dialect for MariaDB only. Then we could detach the support from mysql to mariadb.

Take a look at #219 , let me know what you think

I can definitely give that a look. I'm not sure when I will be able to fully do it as I am busy with college work. However, I will look into it.

[nmggithub]

OK, I am not sure if you noticed, but I am currently in the process of working put a pull request over at the mysqljs repository. Once done there, I can then make a pull request to this repository to add an option in the New Connection dialog, which will allow it to use the new featured added.

[mtxr]

Nice @nmggithub !

No hush. Let's do it in your time.

[mtxr]

@nmggithub any updates on the mysqljs issue?

[nmggithub]

Hey, so sorry. I've been busy and this issue was largely in regards to connecting to the database set up by my school. I have since finished the course, so I don't really necessarily need this issue to be fixed for me personally.

[mtxr]

Thanks for the update @nmggithub. I'll close this since the aforementioned possible solutions works for most of the cases.

If this come up again in the future, we can work on this, but now I'll prioritize some other issues.

[govindasharma1986]

Hi @mtxr,

Just now I too faced this issue. Here's a snippet for it:

ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client

I was trying to connect to our prod mysql server and that's when I faced it. I am able to connect to it from python mysql.connector, sqlalchemy and mysql workbench.

I wished to able to connect to it from vscode for productivity.

I read that instead of mysql package if we use mysql2 then that would solve the issue. I am not in JS so not sure about the fix. Whenever you find time, can you pls look into it?

Thanks

[govindasharma1986]

Hi @mtxr ,

Can we reopen the issue and prioritize it?

Thanks

[PvdBerg1998]

Same issue for me

[scdigitalmedia]

Having the same issue. I've tried the altering user and making updates to the mysql conf file, to no avail. Any other ideas?

[zayne-wang]

Same issue.

Sysinfo

item	version
System	Windows 11 Professional 22H2
mysql	8.0.32
vscode	1.75.0
SQLTools	v0.27.1
SQLTools MySQL/MariaDB	v0.5.1

Settings in SQLTools:

Log from SQLTools:

[1675868679377] INFO  (ext): EXECUTING COMMAND => sqltools.selectConnection
[1675868679377] INFO  (ext): EXECUTING COMMAND => sqltools.getConnections
[1675868679377] INFO  (ls): REQUEST RECEIVED => connection/GetConnectionsRequest
[1675868679380] INFO  (ext): EXECUTING COMMAND => sqltools.getConnections
[1675868679380] INFO  (ls): REQUEST RECEIVED => connection/GetConnectionsRequest
[1675868679381] INFO  (ls): REQUEST RECEIVED => connection/ConnectRequest
[1675868679381] INFO  (ls): Connection instance created for testdb.
    ns: "conn-manager"
[1675868679382] ERROR (ls): {"code":-1,"data":{"driver":"MySQL","driverOptions":{"mysqlOptions":{"authProtocol":"default"}}},"name":"Error"}
    ns: "conn"
[1675868679382] ERROR (ls): Connecting error: {"code":-1,"data":{"driver":"MySQL","driverOptions":{"mysqlOptions":{"authProtocol":"default"}}},"name":"Error"}
    ns: "conn-manager"
[1675868679382] ERROR (ls): Open connection error
    ns: "conn-manager"
[1675868679383] ERROR (ext): ERROR: Error opening connection ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client, {"code":-1,"data":{"driver":"MySQL","driverOptions":{"mysqlOptions":{"authProtocol":"default"}}}}
    ns: "error-handler"

[zayne-wang]

@nmggithub @govindasharma1986 @PvdBerg1998

I don't know if my issue same as yours.

But mine has solved, with following #1095 (comment), and changed the port to 33060, authProtocol to xprotocol and add connectionTimeout as 15 (I think any integer may be valid)

Config in SQLTools