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

COM_CHANGE_USER rejected by MaxScale

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.6
    • Fix Version/s: 2.5.8
    • Component/s: Authenticator
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-123

      Description

      If the client doesn't send the CLIENT_CONNECT_WITH_DB flag in the initial connection but later on does a COM_CHANGE_USER with a default database, MaxScale will reject the COM_CHANGE_USER and close the session.

      It seems that the MariaDB documentation for COM_CHANGE_USER mistakenly stated that the database field is optional when in fact it is always sent in the COM_CHANGE_USER. The solution is to always parse the database field.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration