Bug #105327 | Test Connection in Workbench fails since SSL required | ||
---|---|---|---|
Submitted: | 26 Oct 2021 12:23 | Modified: | 3 Dec 2021 20:44 |
Reporter: | Andrew Watkins | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
Version: | 8.0.27 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | SSL, test, workbench |
[26 Oct 2021 12:23]
Andrew Watkins
[26 Oct 2021 12:53]
MySQL Verification Team
Hello Andrew Watkins, Thank you for the report and feedback. regards, Umesh
[27 Oct 2021 11:32]
MySQL Verification Team
Bug #105340 marked as duplicate of this one
[27 Oct 2021 12:42]
Francisco Granja
In my case not only the test but connection itself becomes unusable. It also happens with any previous connection that you modify.
[28 Oct 2021 12:35]
MySQL Verification Team
Bug #105360 marked as duplicate of this one
[3 Nov 2021 4:25]
MySQL Verification Team
Bug #105429 marked as duplicate of this one.
[3 Nov 2021 7:48]
Dimitar Nikov
Possible workaround: Edit the `connection.xml` file and change `<value type="int" key="useSSL">2</value>` to `<value type="int" key="useSSL">0</value>`. One-liner for Linux: sed -i.bak -e 's/useSSL">2</useSSL">0</g' ~/.mysql/workbench/connections.xml For other OSes you have to point to correct file name, as of: - Windows - %AppData%\MySQL\Workbench\connections.xml - macOS - ~/Library/Application Support/MySQL/Workbench/connections.xml
[4 Nov 2021 17:05]
MySQL Verification Team
Bug #105460 marked as duplicate of this one
[9 Nov 2021 13:23]
MySQL Verification Team
Bug #10550 marked as duplicate of this one
[13 Nov 2021 12:28]
shoujun li
In my case mysql-workbench-community-8.0.27-macos-x86_64.dmg has this issue too.
[3 Dec 2021 20:44]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 8.0.28 release, and here's the proposed changelog entry from the documentation team: Before MySQL Workbench 8.0.27, a connection using SSL attempted to establish an encrypted connection by default if the server supported encrypted connections or to fall back to an unencrypted connection if an encrypted connection could not be established. The default behavior was changed in version 8.0.27 to always require SSL encryption, which could cause a connection test to fail if the server did not support encryption. In addition, the settable values for the Use SSL field no longer included No or If available. This fix restores the previous default behavior (If available) and also restores the full set of Use SSL values for establishing encrypted and unencrypted connections. Thank you for the bug report.