GnuCash
Contact   Instructions
Bug 797045 - Improve error reporting for bad credentials with MySQL backend ("bad or corrupt data" => "access denied")
Summary: Improve error reporting for bad credentials with MySQL backend ("bad or corru...
Status: NEW
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Backend - SQL (show other bugs)
Version: 3.1
Hardware: PC Linux
: Normal trivial
Target Milestone: ---
Assignee: core
QA Contact: core
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-14 06:16 EST by sphakka
Modified: 2019-01-14 06:16 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description sphakka 2019-01-14 06:16:22 EST 
Connecting to a MySQL server with bad credentials fails with a misleading error message:

  "The Server at ... experienced an error or encountered bad or corrupt data"

Instead "mysqld.err" log says:

  "[Warning] Access denied for user ..."

Please, improve error handling and reporting in this scenario. Ideally, prompt again for user/password with correct heading message (this also means using a better face, like bold), f.i.

  " *** Access denied. *** Please try again
     
     Username: ...
     Password:

                     [OK] [Cancel]
  "
Note You need to log in before you can comment on or make changes to this bug.