- Newest
- Most votes
- Most comments
Hi,
This is known issue. Looks like AWS is aware of it and is working on it but no ETA provided. There is already a plan in place to have "default_authentication_plugin" modifiable in the future. Please check the answers to this question.
I tested locally and simply updating the user worked for me.
ALTER USER 'user'@'%' IDENTIFIED WITH caching_sha2_password BY 'password';
Just be careful when applying this to production.
Hi Bruno, the accounts are system accounts I do not have rights to do ALTER USER on.
hello i am facing issue since two months that my DB is taking to much time to Sending to client and it happens randomly any one knows what will be the issue ?
ATTENTION: This operation will not work if you intend to use the rds proxy endpoint read only or read write, because the "Authentication" with Secrets have only Client Authentication type: MySQL Native password.
Confirmed in https://docs.aws.amazon.com/pt_br/AmazonRDS/latest/UserGuide/rds-proxy.html
"RDS Proxy doesn't support the MySQL sha256_password and caching_sha2_password authentication plugins. These plugins implement SHA-256 hashing for user account passwords."
If you use, do you receive this message: Error: "ERROR 1045 (28000): Access denied for user 'DB_USER'@'%' (using password: YES)"
Causes or workarounds: "The Secrets Manager secret used by the proxy doesn't match the user name and password of an existing database user. Either update the credentials in the Secrets Manager secret, or make sure the database user exists and has the same password as in the secret."
"ClientPasswordAuthType": only accept: "MYSQL_NATIVE_PASSWORD" | "POSTGRES_SCRAM_SHA_256" | "POSTGRES_MD5" | "SQL_SERVER_AUTHENTICATION"
Relevant content
- Accepted Answerasked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
Thank you @Joseph!