Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I think I have found the cause of this issue: Changes default behavior of driver to not validate server certificate if client did not request encryption with "encrypt=true" but encryption was en...
Answer
#2: Post edited
- I think I have found [the cause of this issue](https://github.com/dotnet/SqlClient/pull/391):
- > Changes default behavior of driver to not validate server certificate if client did not request encryption with "encrypt=true" but encryption was enforced by SQL Server.
This is also mentioned in the [SQL Client 2.0 breaking changes](https://github.com/dotnet/SqlClient/blob/main/release-notes/2.0/2.0.0.md#breaking-changes-1).
- I think I have found [the cause of this issue](https://github.com/dotnet/SqlClient/pull/391):
- > Changes default behavior of driver to not validate server certificate if client did not request encryption with "encrypt=true" but encryption was enforced by SQL Server.
- This is also mentioned in the [SQL Client 2.0 breaking changes](https://github.com/dotnet/SqlClient/blob/main/release-notes/2.0/2.0.0.md#breaking-changes-1):
- > The driver will now perform Server Certificate validation when TLS encryption is enforced by the target Server, which is the default for Azure connections
#1: Initial revision
I think I have found [the cause of this issue](https://github.com/dotnet/SqlClient/pull/391): > Changes default behavior of driver to not validate server certificate if client did not request encryption with "encrypt=true" but encryption was enforced by SQL Server. This is also mentioned in the [SQL Client 2.0 breaking changes](https://github.com/dotnet/SqlClient/blob/main/release-notes/2.0/2.0.0.md#breaking-changes-1).