I have a user set up with mysql_native_password authentication, verified here:
mysql> select user, plugin from mysql.user where user="testuser";
+----------+-----------------------+
| user | plugin |
+----------+-----------------------+
| testuser | mysql_native_password |
+----------+-----------------------+
I also made sure to flush privileges to ensure everything was updated on MySQL's side, but when I try to log in, it's still giving me an ER_NOT_SUPPORTED_AUTH_MODE.
MySQL v8.0.19
Library version 2.18.1
Hi @Rodentman87 over this weekend I was tracking down a similar issue and so was just getting the plugin auth working on this module, which seems to fix the issue. I'll push up a test branch for you to try to validate this tomorrow (my time; approx 8 hours from now) and then let me know how it works out for you.
Hi, Also I am getting this error when user name is wrong
Error: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
@dougwilson any update on that test branch?
?
Use this module support mysql_native_password npm install mysql8.0
I got same Error!
Error: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
MYSQL VERSION: mysql Ver 8.0.19 for Linux on x86_64 (MySQL Community Server - GPL)
mysqljs-version: 2.18.1
mysql> SELECT plugin FROM mysql.user WHERE User = 'root';
+-----------------------+
| plugin |
+-----------------------+
| mysql_native_password |
| mysql_native_password |
+-----------------------+
2 rows in set (0.00 sec)
Hey everyone, I just wanted to say I haven't forgot about this; I recently changed jobs and of course during that process can be a bit hectic. I will get my test changed pushed up here as a branch so you folks can test it on your set ups to check if it resolves your issue or we need to dig further. I am heading to sleep right now, but after work on Friday I will make the time to work through this issue in this module with anyone around 馃憤
Hey, just wondering if there was any updates on this yet. I ended up using something else temporarily, but this issue also seems to be affecting dependent libraries (in my case prisma).
Same issue here. Were you able to resolve this?
Same issue.
Most helpful comment
Hey everyone, I just wanted to say I haven't forgot about this; I recently changed jobs and of course during that process can be a bit hectic. I will get my test changed pushed up here as a branch so you folks can test it on your set ups to check if it resolves your issue or we need to dig further. I am heading to sleep right now, but after work on Friday I will make the time to work through this issue in this module with anyone around 馃憤