Your program which uses a MySQL connector receives this error: Client does not support authentication protocol request by server The account running the program uses caching_sha2_password. Which two…

Question

Options

• ADisable TLS/SSL authentication.
• BPlace this in the root directory of your shell account:
• CUse blank RSA or SSL certificates.
• DUpgrade the connector to a version that supports caching_sha2_password.
• EChange the user account to use mysql_native_password.

• A
  3% (1)
• B
  11% (4)
• C
  6% (2)
• D
  80% (28)

Explanation

MySQL 8.0 introduced caching_sha2_password as the default authentication plugin, which older connectors don't understand - upgrading the connector (D) to a version that supports this protocol solves the problem at the client level. Alternatively, changing the user to mysql_native_password (E) downgrades authentication to the older protocol that legacy connectors already understand, solving it at the server/account level.

Why the distractors are wrong:

• A - TLS/SSL is a transport encryption layer, entirely separate from the authentication plugin mechanism; disabling it doesn't change how passwords are verified.
• B - The choice is incomplete (no file is specified), but placing config files in a shell home directory does not resolve a server-side authentication protocol mismatch.
• C - Blank or self-signed certificates relate to SSL/TLS identity verification, not to which password hashing algorithm the server uses for login.

Memory tip: Think of it as a handshake mismatch - you have two options: teach the client the new handshake (upgrade the connector) or tell the server to use the old handshake for that user (switch to mysql_native_password). Everything else (TLS, certs) is a different conversation entirely.

No community discussion yet for this question.