Documentation Home
MySQL Connector/NET Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb

MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/NET Version 8.x  /  Changes in MySQL Connector/NET 8.0.27 (2021-10-19, General Availability)

Changes in MySQL Connector/NET 8.0.27 (2021-10-19, General Availability)

Functionality Added or Changed

  • Previously, Connector/NET implemented the authentication_kerberos_client plugin to support Kerberos authentication for classic MySQL protocol connections made by applications running on Linux. Support is now extended to Windows using the Security Support Provider Interface (SSPI) for classic MySQL protocol connections (see Connector/NET Authentication). (WL #14654)

  • Connector/NET now supports Oracle Cloud Infrastructure pluggable authentication for classic MySQL protocol connections. The exchange of a signed token between the authentication_oci plugin and the client-side plugin enables .NET applications to access MySQL Database Services within a specific tenancy in a secure way without using a password. This feature is restricted to applications that target .NET Standard 2.0 (.NET Framework 4.5.x implementations are not supported).

    For more information about Oracle Cloud Infrastructure authentication, see Connector/NET Authentication. (WL #14708)

Bugs Fixed

  • Connections made to MySQL 5.6 using sockets and the default SSL mode (Preferred) failed instead of providing an unsecured connection. (Bug #33191344)

  • Transactions started by the SHOW COLLATION statement on all MySQL 8.0 server versions were not closed when the autocommit system variable was set to zero. The ongoing transaction generated an error. (Bug #33123597)

  • Attempts to call a fully qualified procedure using the schema.procedure syntax with single quotation marks around the schema name, procedure name, or both produced an exception. (Bug #33097912)

  • When querying a CHAR(36) column, reading a non-NULL value could emit an error if MySqlCommand was part of the prepared statement. (Bug #32938630, Bug #103390)