MySQL Bugs: #83360: PASSWORD DIALOG PROBLEM

Bug #83360	PASSWORD DIALOG PROBLEM
Submitted:	13 Oct 2016 2:27	Modified:	13 Nov 2016 11:28
Reporter:	MANIKANDAN THIYAGARAJAN	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S5 (Performance)
Version:	6.3.7	OS:	Windows (Microsoft Windows 10 Home Single Language)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Caps, MySQL Workbench, password

Description:
MySQL Workbench password dialog is annoying.  My Workbench often asks for password every 5 minutes once.  This may be due to my internet connection resetting again and again.  BUT THE PROBLEM IS, when I re-enter my password to get connected again, there is no CAPS LOCK indicator in the password dialog, so I input a wrong password by mistake (unfortunately my wireless keyboard also does not have CAPS indicator).

When I input a wrong password, MySQL Workbench is not giving any error but gets confused and freezes.  I literally have to use Task Manager to close and restart Workbench.

How to repeat:
1. Download MySQL Workbench 6.3.7.
2. Install and connect to any database.  Do not store the password in Vault.
3. After connected to database, disconnect the Internet connection.
4. After few seconds, reconnect to Internet.
5. MySQL Workbench will prompt you to enter a password.
6. Enter a wrong password now.

You can see the application freezing and getting confused.

Suggested fix:
Simple, MySQL Workbench password dialog MUST have a CAPS LOCK indicator.

MySQL Workbench must handle wrong passwords properly.

Hello MANIKANDAN,

Thank you for the bug report.
I could not see any issues with password dialog box and it is clearly displaying message as caps lock is "ON" and clearly displaying access denied error message while enter wrong password.

Thanks,
Chiranjeevi.

Screenshot

Attachment: 83360.jpg (image/jpeg, text), 160.87 KiB.

Screenshot

Attachment: 83360_1.JPG (image/jpeg, text), 151.97 KiB.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".