-
Notifications
You must be signed in to change notification settings - Fork 426
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
SQL Server Always Encrypted feature with KeyVault and MSI #1069
Comments
Hi @venkatareddym In order to work with Always Encrypted feature, you can choose one of three methods:
Documentation Reference: |
We already using an Always Encrypted feature with Key Vault with ClientId and ClientSecret. We want to eliminate the ClientId and ClientSecret with the Azure app services MSI feature. For SQL server we already using Azure App services MSI feature. Our main goal is to eliminate the secrets and passwords on config files. We are checking examples for SQLServerKeyVaultAuthenticationCallback with Keyvalut MSI ( Managed Service Identity )features. |
Hi @venkatareddym Yes, that is not supported by driver yet. As of now MSI is only supported for acquiring access token for Azure database connection. I will keep the issue open until we support Azure Key Vault access with MSI in the driver. |
Hi, @venkatareddym, you can get the Azure Key Vault access token using the AzureServiceTokenProvider (from Microsoft.Azure.Services.AppAuthentication 1.2.0 preview). The GetToken method:
|
@cheenamalhotra @venkatareddym @ronneyramon I too like this feature to be implemented in JDBC driver. This is analogous to IntegratedSecurity=true in a connection string which automatically initiates Windows Security based connection to SQL Server. Like wise, If a Connection String Keyword IntegratedKeyVaultSecurity=true (or any meaningful keyword) is introduced to wrap registration of KeyVaultProvider (GetToken callback) it would be of great help. From JDBC driver version 7.4.1 onwards, AzureKeyVaultProvider is automatically registered if two Connection String Keywords present keyVaultProviderClientId, keyVaultProviderClientKey (#902) eliminating the need for writing the below code.
|
hi all, as of the latest 8.3.0 preview release the driver added support for authentication to AKV using Managed Identity. Here is a wiki on how to use this feature. Please give this a try and let us know if you have any questions. I'll close this feature request issue now if any questions or problems please open a new issue. Thanks.. |
Question
We are trying to use SQL Server Always Encrypted feature with KeyVault and MSI. Azure App Service MSI feature is used on the database on KeyVault. Please provide an example without keyvault ClientId and ClientSecret.
We have a working solution based on keyvault ClientId and ClientSecret, But we are checking a solution without using ClientId and ClientSecret.
Relevant Issues and Pull Requests
The text was updated successfully, but these errors were encountered: