Skip to content
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

Feature | AKV Provider Upgrade to use new Azure key Vault libraries #630

Merged
merged 25 commits into from
Feb 26, 2021

Conversation

cheenamalhotra
Copy link
Member

@cheenamalhotra cheenamalhotra commented Jun 30, 2020

Addresses #294

Changes full design and introduces new constructors to accept implementation of TokenCredential to support new libraries.

Breaking Changes:

  • Drops support for .NET Framework 4.6, supports .NET Framework 4.6.1+
  • Drops support for old constructors that accepted "AuthenticationCallback".

cc @Xtrimmer

[6 Aug, 2020] Update:
The old constructors are now removed totally and driver does not implement/support authentication callback in new design now. For user applications willing to support multi-user credentials for acquiring tokens, can implement a custom TokenCredential class with their own logic in "GetToken" and "GetTokenAsync" APIs. An example has been added (doc/samples/AzureKeyVaultProviderLegacyExample_2_0.cs) to the repository to demonstrate the same, will be published to Microsoft Docs.

@cheenamalhotra cheenamalhotra added 🆕 Public API Use this label for new API additions to the driver. 🔨 Breaking Change Use this label for breaking API changes in the driver. labels Jul 7, 2020
Copy link

@heaths heaths left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only reviewed the production code using Key Vault packages directly and overall it looks okay, but I'm curious why it's all implemented synchronously? Where necessary, you're calling async over sync (and in some places, in ways that can deadlock) but wouldn't it make for a more efficient package for callers to use async?

@cheenamalhotra
Copy link
Member Author

I believe the reason of synchronous methods only is the class SqlColumnEncryptionKeyStoreProvider.
I think it would be possible to extend this to also support counter Async APIs, @Xtrimmer any thoughts?

# Conflicts:
#	src/Microsoft.Data.SqlClient/add-ons/Directory.Build.props
#	src/Microsoft.Data.SqlClient/tests/ManualTests/AlwaysEncrypted/TestFixtures/Setup/ColumnMasterKey.cs
#	src/Microsoft.Data.SqlClient/tests/ManualTests/Microsoft.Data.SqlClient.ManualTesting.Tests.csproj
@cheenamalhotra cheenamalhotra added the 📦 AKV Provider Add-on: Azure Key Vault Provider related label Oct 13, 2020
@cheenamalhotra cheenamalhotra merged commit c2b4df7 into dotnet:master Feb 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 Breaking Change Use this label for breaking API changes in the driver. 🆕 Public API Use this label for new API additions to the driver. 📦 AKV Provider Add-on: Azure Key Vault Provider related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AzureKeyVaultProvider should move to the latest Azure KeyVault Libraries
6 participants