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

MaxCtrl cluster sync doesn't work with encrypted passwords

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.11
    • 2.2.9
    • maxctrl
    • None

    Description

      Overview

      When encrypted passwords are used with the MaxCtrl cluster sync command, the passwords are sent encrypted with the key on the source MaxScale. If the destination MaxScales have different encryption keys, the password decrypts into garbage.

      Step to Reproduce

      • Use encrypted passwords on two MaxScale instances with different encryption keys
      • Alter the password of a service, monitor or server on one MaxScale
      • Execute maxctrl cluster sync
      • Restart second MaxScale →results in an error

      Attachments

        Activity

          People

            Unassigned Unassigned
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.