[MXS-1573] Maxscale local user cache corrupt Created: 2017-12-06  Updated: 2018-11-27  Resolved: 2018-11-27

Status: Closed
Project: MariaDB MaxScale
Component/s: cache
Affects Version/s: 2.1.11
Fix Version/s: 2.2.2

Type: Bug Priority: Minor
Reporter: Maikel Punie Assignee: Timofey Turenko
Resolution: Fixed Votes: 0
Labels: None
Environment:

centos7, 3.10.0-693.5.2.el7.x86_64



 Description   

We had a problem that users could not authenticate via maxscale, after some debugging it only happened if the user had db specific permissions, if the user has global permissions all worked perfectly.

After removing the dbusers.db file on <svc>/<listener>/cache directory it was solved.



 Comments   
Comment by Johan Wikman [ 2017-12-07 ]

tturenko Could you try to repeat this.

Comment by Maikel Punie [ 2017-12-11 ]

This was on a production system, so its not possible to use this system for testing.
On our dev setup we have not seen this.

Also the system was running stable for 6 months, nothing changed in the config during that time, only maxscale was upgraded in that timeframe.

Comment by markus makela [ 2018-11-27 ]

Fixed by the authenticator refactoring in 2.2

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