-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect when OS has TLS1.3 (and TLS1.2) enabled #1151
Comments
Hi @Rans4ckeR I'm able to reproduce the issue as well and will update you as I have a fix. |
@DavoudEshtehari is it already known how this will be fixed? Will it somehow be possible to explicitly set the list of allowed TLS versions in similar fashion to HttpClientHandler.SslProtocols? |
Hi @Rans4ckeR Currently, we are looking into fixing the driver to fallback on TLS 1.2.
It is something to think about, we haven't considered it yet. |
Interestingly, System.Data.SqlClient seems unaffected.. |
Describe the bug
After enabling TLS1.3 in the OS (for both client and server) the connection fails.
TLS1.2 is also enabled.
Client & server run on the same machine.
To reproduce
Expected behavior
The client should connect using TLS1.3 or if not supported fallback to a lower enabled TLS version.
Side note for EF: SqlServerDbContextOptionsBuilder should allow me to specify the acceptable TLS version(s) (similar to HttpClient).
Further technical details
Microsoft.Data.SqlClient version: 3.0.0
.NET target: net6.0-preview.5
SQL Server version: Microsoft SQL Server Developer (64-bit) 15.0.4138.2
Operating system: Windows 10 Pro 21H1 19043.1081
Additional context
-SSMS 18.9.1 can connect without problem.
-Azure Data Studio 1.30.0 fails with the same exception since it also uses Microsoft.Data.SqlClient.
The text was updated successfully, but these errors were encountered: