[MXS-2648] user authentication not working in maxscale 2.4 Created: 2019-08-26  Updated: 2019-09-13  Resolved: 2019-08-30

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.4.1
Fix Version/s: 2.4.2

Type: Bug Priority: Major
Reporter: Anoop P Alias Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None
Environment:

Centos7


Sprint: MXS-SPRINT-89

 Description   

[MySQL-Monitor]
type=monitor
module=mariadbmon
servers=server1,server2
user=maxscale
password=xxxxx
monitor_interval=10000

Throws error
error : [MariaDBAuth] [XtendWeb] Failed to connect to server 'server1' ([127.0.0.1]:13306) when checking authentication user credentials and permissions: 1045 Access denied for user 'maxscale'@'localhost' (using password: YES)

But
mysql -umaxscale -pxxxxx
works just fine

Pretty sure this is an issue with Maxscale 2.4 version as if I downgrade maxscale to 2.3, maxscale start with the same exact config

 Comments   
Comment by Esa Korhonen [ 2019-08-28 ]

Possibly linked to https://jira.mariadb.org/browse/MXS-2650
Was SSL being used for monitor and/or service user?

Comment by Anoop P Alias [ 2019-08-28 ]

Yes SSL is used on the server declaration

[server1]
type=server
address=127.0.0.1
port=13306
protocol=MariaDBBackend
ssl=required
ssl_version=MAX
ssl_ca_cert=/etc/mysql-ssl/ca-cert.pem
ssl_cert=/etc/mysql-ssl/client-cert.pem
ssl_key=/etc/mysql-ssl/client-key.pem
persistpoolmax=100
persistmaxtime=3600

[MySQL-Monitor]
type=monitor
module=mariadbmon
servers=server1,server2
user=maxscale
password=2D60490999869453A4A3A905BCF71D8636E1A2A62805EA25B5F9F9A4F08EEB37
monitor_interval=10000

As mentioned the same config works perfectly in 2.3

Comment by Esa Korhonen [ 2019-08-30 ]

Closing for now as this is likely fixed in 2.4.2. Please reopen if that is not the case.

Comment by Anoop P Alias [ 2019-08-30 ]

I can confirm this is indeed fixed in 2.4.2

Generated at Thu Feb 08 04:15:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.