-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fully support mysql 8.0 (caching_sha2_password
authentication)
#178
Comments
@ryanpeters-google @XinranTang I would greatly appreciate your feedback on this, or if you could tag whoever is the current maintainer of the project. |
Hi Mathew, thanks for raising this issue. We will take MySQL 8.0 migration into consideration. |
We have upgraded mysql db from 5 to 8 and now its causing issue related to mlmd authentication plugin. i think kfp uses mysql_native_password type whereas mlmd requires caching_sha2_password. could anyone please how to overcome this? Is it possible to change mlmd to kfp like mysql_native_password ? |
Currently,
ml-metadata
can't be used with most MySQL 8.0 databases out of the box, this is because in MySQL 8.0, thedefault-authentication-plugin
was changed frommysql_native_password
tocaching_sha2_password
for significant security reasons.There have been a number of issues related to this over the past few years:
We even have an error message that suggests people use the less secure
mysql_native_password
:ml-metadata/ml_metadata/metadata_store/mysql_metadata_source.cc
Lines 173 to 181 in 2d7a260
As the adoption of MySQL 8.0 increases, and we hit the EOL of MySQL 5.7 in October 2023, this issue is going to affect more and more people.
I strongly suggest we plan to upgrade our MySQL client to one which properly supports MySQL 8.0.
The text was updated successfully, but these errors were encountered: