We realize this will cause some disruption, but letting clients try to connect without encryption by default leaves them open to attack from malicious actors. Similar to the HTTP to HTTPS default changes made in web browsers a few years back (and the security reasons for them), we are changing the default value of the `Encrypt` connection option from `false` to `true`. With the increased emphasis on secure-by-default, the growing use of cloud databases, and the need to ensure connections are secure, it's time for this backwards-compatibility-breaking change. There a couple breaking changes in 10.2 over previous releases that may affect a lot of users. Fixed TDSParser stuck on TDS_COLMETADATA issue, which could result in a hang for certain queries ( #1662)īreaking Changes Encrypt = true, by default.
Added 4219 to transient error list 1643.Added check for closed statement to registerColumnEncryptionKeyStoreProvidersOnStatement 1644.Support for multi user scenarios for Always Encrypted key store providers 1614 ( read more).Idle Connection Resiliency Feature 1669 ( read more).Version 10.2.0 brings several added features, changes, and fixed issues over the previous production release. Version 10.2 of the Microsoft JDBC Driver for SQL Server has been released.