Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4093

User account manager does not detect db-level priv changes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.19, 6.2.4
    • Fix Version/s: 2.5.20
    • Component/s: mariadbclient
    • 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.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            esa.korhonen Esa Korhonen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.