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

MaxScale returns different error messages for authentication failures

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.5.0
    • Authenticator
    • None

    Description

      The error messages are not consistent with a direct connection:

      Non-existent user
      Wrong error: `Access denied for user 'not-a-user'@'' (using password: YES) to database 'test'` (original: `Access denied for user 'not-a-user'@'' (using password: YES)`)
      0.074041: TEST_FAILED! readwritesplit returned wrong error
      Wrong error: `Access denied for user 'not-a-user'@'' (using password: YES) to database 'test'` (original: `Access denied for user 'not-a-user'@'' (using password: YES)`)
      0.074056: TEST_FAILED! readconnroute returned wrong error
      Wrong password
      No permissions on database
      Wrong error: `Access denied for user 'bob'@'' (using password: YES) to database 'error_messages'` (original: `Access denied for user 'bob'@'' to database 'error_messages'`)
      0.128459: TEST_FAILED! readwritesplit returned wrong error
      Wrong error: `Access denied for user 'bob'@'' (using password: YES) to database 'error_messages'` (original: `Access denied for user 'bob'@'' to database 'error_messages'`)
      0.128474: TEST_FAILED! readconnroute returned wrong error
      

      There is a test case for this, error_messages, where the success criteria is inverted. Once this is fixed, the test also needs to be updated.

      Attachments

        Activity

          People

            Unassigned Unassigned
            markus makela markus makela
            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.