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

Database change not allowed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.6
    • Fix Version/s: 2.1.10, 2.2.0
    • Component/s: dbfwfilter
    • Labels:
      None
    • Environment:
      CenOS 7.2

      Description

      The change database command, used as when using the "use" command from the commandlind or using mysql_select_db() command are not allowed unless there is a rule for that matches the specific name of the database, when using dbfwfilter. One can connect to any database, that is not the problem, but changing the database in the middle of the section requires that there is a rule that allos that specific database. The SQL Command that is parsed seems to be just the name of the database. For example, to allow use of the "use test" command to change to the "test" database, a rule similar to this is required:
      rule allow_test deny regex '^test$'
      This does not really make sense, as you can still connect to any database that the user has access to, by specifying that when connecting, it is only when changing database that this rule makes any sense.
      I would suggest that mysql_select_db() is instead mapped to the string "use <database name>" which would make a lot more sense. Alternatively, this could be ignored and database access being handled by the database server.

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            karlsson Anders Karlsson
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.