RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug was initially created as a copy of Bug #1849812

I am copying this bug because: 

mariadb-java-client was updated to 2.7.1 in RHEL-7, so we have a regression in RHEL-8 now. We should figure out how to close this gap (whether the rebase would be acceptable in RHEL-8 or whether to include a new package).


Description of the original problem (RHEL-7):
Would be good if the mariadb-java-client distributed on rhel is greater than version 2.5, on this version support to the 'caching_sha2_password' on the client side, the current version does not support it thus we need to configure the MySQL or Mariadb newer versions to use the old authentication plugin: mysql_native_password

Version-Release number of selected component (if applicable):
mariadb-java-client: 2.2.5


How reproducible:
Use this driver to connect to a MySQL 8 database.



Steps to Reproduce:
Try to connect an application to the MySQL 8 database with the caching_sha2_password authentication plugin enabled (defualt).


Actual results:
App fails to connect to the database.

Expected results:
A successful connection must happen.


Additional info:
Workaround is to switch back to the old authentication plugin: mysql_native_password

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (mariadb-java-client bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7562