You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with **v2.0.0**, the `Microsoft.Data.SqLClient.AlwaysEncrypted.AzureKeyVaultProvider` supports the new Azure.Core and Azure.Identity APIs to perform authentication with Azure Key Vault. An instance of [`TokenCredential`](/dotnet/api/azure.core.tokencredential) implementation can now be passed to [`SqlColumnEncryptionAzureKeyVaultProvider`](/dotnet/api/microsoft.data.sqlclient.alwaysencrypted.azurekeyvaultprovider.sqlcolumnencryptionazurekeyvaultprovider) constructors to initialize Azure Key Vault provider object.
338
+
327
339
For examples demonstrating performing encryption/decryption with Azure Key Vault, see [Azure Key Vault working with Always Encrypted](azure-key-vault-example.md) and [Azure Key Vault working with Always Encrypted with secure enclaves](azure-key-vault-enclave-example.md).
328
340
329
341
### Implementing a custom column master key store provider
New stable (GA) releases are published on demand when new features are added. Long Term Support (LTS) releases will be chosen by stakeholders and maintainers based on a few qualifications and customer response.
47
+
48
+
### Actively supported releases
49
+
50
+
| Version | Official Release Date | Latest Patch Version | Patch Release Date | Support Level | End of Support |
51
+
| -- | -- | -- | -- | -- | -- |
52
+
| 2.x | March 3, 2021 | 2.0.0 | March 3, 2021 | LTS | March 4, 2024 |
53
+
| 1.x | November 19, 2019 | 1.2.0 | December 01, 2020 | LTS | November 21, 2022 |
54
+
55
+
56
+
## Long Term Support (LTS) releases
44
57
45
58
LTS releases are supported for three years after the initial release.
46
59
47
-
###Current releases
60
+
## Current releases
48
61
49
62
Current releases are supported for three months after a subsequent Current or LTS release.
50
63
64
+
51
65
## SQL version compatibility with Microsoft.Data.SqlClient
52
66
53
67
|Database version →<br />↓ Driver Version|Azure SQL Database|Azure Synapse Analytics|Azure SQL Managed Instance|SQL Server 2019|SQL Server 2017|SQL Server 2016|SQL Server 2014|SQL Server 2012|
Copy file name to clipboardExpand all lines: docs/connect/ado-net/sqlclient-troubleshooting-guide.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "SqlClient troubleshooting guide"
3
3
description: "Page that provides resolutions to commonly observed problems."
4
-
ms.date: "11/27/2020"
4
+
ms.date: "03/03/2021"
5
5
dev_langs:
6
6
- "csharp"
7
7
- "vb"
@@ -167,6 +167,13 @@ at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception
167
167
168
168
**Recommended Solution:** Generate a new TLS/SSL Certificate for the server whose hash is signed with at-least the SHA-256 hashing algorithm.
169
169
170
+
- Tightly restricted cipher suites on Linux with .NET 5+
171
+
172
+
.NET 5 introduced a breaking change for Linux clients, where a tightly restricted list of permitted cipher suites is used by default. You may need to expand the default cipher suite list to accept legacy clients (or to contact legacy servers) by either specify a `CipherSuitePolicy` value or changing the _OpenSSL_ configuration file.
173
+
174
+
Read more on [Default TLS cipher suites for .NET on Linux
175
+
](/dotnet/core/compatibility/cryptography/5.0/default-cipher-suites-for-tls-on-linux) for recommended action.
0 commit comments