Bug 1849812 - rh-mariadb105: Update mariadb-java client to 2.5+
Summary: rh-mariadb105: Update mariadb-java client to 2.5+
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: mariadb-java-client
Version: rh-mariadb105
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: alpha
: 3.6
Assignee: Ondrej Dubaj
QA Contact: Jakub Heger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-22 20:51 UTC by Spolti
Modified: 2023-08-09 09:50 UTC (History)
5 users (show)

Fixed In Version: rh-mariadb105-mariadb-java-client-2.7.1-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-03 11:15:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker KIECLOUD-396 0 Major Open Follow up task for update MariaDB driver on KIE Server image. 2020-12-02 10:59:42 UTC

Description Spolti 2020-06-22 20:51:55 UTC
Description of problem:
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

Comment 8 Spolti 2020-12-02 13:46:34 UTC
Hi @hhorak, sry for the delay, and thanks for your reply.
At this point, I think we can wait the normal release flow. I thought there would be customer asking for it, but so far we haven't.

For people that are hitting the issue related with the security we are suggesting to use that workaround.

Comment 17 errata-xmlrpc 2021-06-03 11:15:45 UTC
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 (new packages: rh-mariadb105), 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/RHEA-2021:2217


Note You need to log in before you can comment on or make changes to this bug.