Unable to log in with MySQL 8.0.11; caching_sha2_password authentication method unknown to the client

[ibennetch]

With MySQL 8.0.11 I'm unable to log in with users that had been working fine under previous versions (at least 8.0.0, perhaps even more recent than that).

mysqli_real_connect(): The server requested authentication method unknown to the client [caching_sha2_password]

mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client

See also https://dev.mysql.com/doc/refman/8.0/en/authentication-plugins.html

I'm using QA_4_8.

[ibennetch]

See also https://stackoverflow.com/questions/49948350/phpmyadmin-on-mysql-8-0

[ibennetch]

Possibly related: #14217

[ibennetch]

A point release seems like a bad time to make changes to the authentication protocols. I've been testing with 8.0.4-rc which works fine, and now that 8.0.11 is out it causes problems.

[Gemorroj]

https://bugs.php.net/bug.php?id=76243

[ozeer]

I met this issue a few days before, is there anyone who solve this problem? thanks a lot~

[mauriciofauth]

There is not much we can do about it right now, as apparently PHP still does not support the caching_sha2_password authentication method.

However, I was able to connect successfully using other authentication methods such as mysql_native_password and sha256_password.

[szabacsik]

https://stackoverflow.com/questions/49948350/phpmyadmin-on-mysql-8-0/50437307#50437307

[mauriciofauth]

PHP developers started adding caching_sha2_password support. Once a version of PHP with this support is released, we can add support for caching_sha2_password on our side as well.

[rmanibus]

Upgrading to PHP7.2.7 solved the issue for me.

[donpaul120]

@rmanibus i have php 7.2.7 and mysql Ver 8.0.11 but im wondering why it doesn't work still.

[Apollo725]

I expired root user and reinstall all of the mysql workspace, then I got this error.
Warning: mysqli_connect(): The server requested authentication method unknown to the client [caching_sha2_password] in /Volumes/Workspace/workspace/test/php_test/Simple-PHP-Login/add.php on line 3

I was using mac and didn't use xampp.

[hkrware]

php-fpm 7.2.11 and mysql 8.0.12 both on centos 7.5.1804 x64 and not working with phpmyadmin 4.8.3

[mauriciofauth]

As mentioned earlier, there is not much we can do about it at this time.
The mysqlnd library does not support the caching_sha2_password authentication method yet.
An alternative would be to use the libmysqlclient library, however PHP does not support the libmysqlclient library of MySQL 8 yet.

So the real alternative, for now, is to use another authentication method other than caching_sha2_password.

[SugarD-x]

I'm not sure if this helps anything, but on MySQL Server 8.0.12, I'm getting this error ONLY when upgrading to PHP 7.2.11. (It doesn't just affect PHPMyAdmin). When I revert back to PHP 7.2.8, I have no problems. Seems a bit odd that a newer version of PHP would cause this.

I know downgrading PHP is probably not the greatest idea, but if this helps anyone as a temporary solution, it is there.

[mauriciofauth]

@SugarD-x This is related to commit php/php-src@d6e81f0 which was later reverted by php/php-src@03740ef.

[SugarD-x]

@mauriciofauth Thank you! That definitely explains my issue.

[doveraudio]

I used this to get it back when I started a new dev server with mysql 8 and php 7.3
ALTER USER root@localhost IDENTIFIED WITH mysql_native_password BY 'PASSWORD';

it seems to be working ok so far.

[SugarD-x]

@doveraudio That is the workaround, not an actual fix. That just updates your root database login to use the old password authentication method, rather than this new one.

[p8ul]

https://stackoverflow.com/questions/49948350/phpmyadmin-on-mysql-8-0

I was able to connect successfully using other authentication methods such as mysql_native_password
By running this command on mysql on the terminal.
cd /usr/local/mysql/bin
./mysql -u root -p
Run command below on msql terminal
CREATE USER sky@localhost IDENTIFIED WITH mysql_native_password BY 'password'

[SugarD-x]

As I just said previously:

That is the workaround, not an actual fix. That just updates your root database login to use the old password authentication method, rather than this new one.