[MXS-3222] Authentication failed for older clients after upgrading to 2.5.4 Created: 2020-10-02  Updated: 2021-02-15  Resolved: 2021-02-15

Status: Closed
Project: MariaDB MaxScale
Component/s: Authenticator
Affects Version/s: 2.5.4
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Maikel Punie Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

centos 7, python MySQLdb 1.3.10



 Description   

after upgrading from 2.4 to 2.5 series of maxscale older clients get the following error:

2020-10-02 14:48:29 warning: (7131) [mariadbclient] Authentication failed for user 'centralqueue'@[138.203.8.180] to service 'ReadSVC'. Originating listener: 'ReadLST-129'. MariaDB error: 'Access denied for user 'centralqueue'@'138.203.8.180' (using password: YES)'.

downgrading to 2.4 solves the problem



 Comments   
Comment by markus makela [ 2020-11-09 ]

What connector do you use?

Comment by Maikel Punie [ 2020-11-09 ]

python MySQLdb 1.3.10

Comment by markus makela [ 2020-11-24 ]

Can you execute SHOW GRANTS for that user?

Comment by Maikel Punie [ 2020-11-24 ]

MariaDB [(none)]> show grants for centralqueue@'%';
-------------------------------------------------------------------------------------------------------------

Grants for centralqueue@%

-------------------------------------------------------------------------------------------------------------

GRANT USAGE ON . TO `centralqueue`@`%` IDENTIFIED BY PASSWORD '*9AEE5DB1EE0AB49373ADEAFBFCF8F0E4063F03A3'
GRANT SELECT, EXECUTE, SHOW VIEW ON `regressiondb`.* TO `centralqueue`@`%`

-------------------------------------------------------------------------------------------------------------
2 rows in set (0.000 sec)

Comment by markus makela [ 2020-12-29 ]

Maikel Punie does this happen with the latest release?

Comment by Maikel Punie [ 2021-01-22 ]

with the latest version this seems to be solved

Comment by markus makela [ 2021-02-15 ]

Closing as this seems to have been fixed, as mentioned by Maikel Punie.

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