[MXS-4093] User account manager does not detect db-level priv changes Created: 2022-04-13  Updated: 2022-04-21  Resolved: 2022-04-20

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbclient
Affects Version/s: 2.5.19, 6.2.4
Fix Version/s: 2.5.20

Type: Bug Priority: Major
Reporter: Esa Korhonen Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None


 Description   

If a login to MaxScale fails and user account fetching is not limited by "users_refresh_time", MaxScale fetches user accounts and grants from the server. MaxScale then checks if the new data differs from existing data and updates its cache if yes (updating can be a somewhat heavy operation so best done only when needed).

The comparison operation does not correctly detect changes in the "mysql.db"-array and thinks that the new data is identical to the old even when not. Thus, the data is not updated. Changes in other grant types (e.g. table-level or a new user) are detected properly and will cause the entire grant database to update. Will be fixed in 2.5.20 & 6.4.1.


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