本文介绍了始终使用Azure Key Vault SSMS清除错误加密的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试使用Azure Key Vault设置一个新的Always Encrypted数据库(我以前已经完成过此工作)。在 SSMS始终加密向导中,我可以选择要加密的表和列,但是在选择 Azure Key Vault作为密钥存储提供者后遇到了问题。我登录后,窗口简短地弹出了一个下拉列表,该下拉列表正确列出了我在Azure中的Key Vault,但是它立即消失了,并带有一个警告三角形,旁边带有单词 Purge和 Try Again按钮。



单击详细信息显示:



有什么想法,意味着什么以及如何完成向导?



我已经在2种不同的SQL 2016安装中尝试了相同的结果,并使用来自不同机器的SSMS。



我知道它说我们在连接到Azure时遇到了问题,但是由于它正在登录并(简短地)列出我的关键文件库,连接问题可能是什么? / p>

谢谢。






部分细节



================================



我们在连接到Azure时遇到了问题(我们在连接到Azure时遇到了问题)



========= ================



清除(Microsoft.SqlServer.Management.ServiceManagement )






程序位置:



在Microsoft.SqlServer。 Management.ServiceManagement.ResourceManagement.AzureKeyVaultKeyPermissionEnumConverter.ReadJson(JsonReader reader,Type objectType,Object existValue,JsonSerializer serializer)
在Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter转换器,JType对象ue)
在Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list,JsonReader reader,JsonArrayContract contract,JsonProperty containerProperty,String id)在Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(Jist。类型objectType,JsonContract合同,JsonProperty成员,对象existValue,字符串ID)



在此处添加SSMS版本详细信息:
Microsoft SQL Server Management Studio 13.0.16106.4
Microsoft Analysis Services客户端工具13.0.1700.441
Microsoft数据访问组件(MDAC)10.0.15063.0
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.11.15063.0
Microsoft .NET Framework 4.0.30319.42000
操作系统6.3.15063

解决方案

我能够通过在Vault中创建KEY来解决此问题,用脚本从库中引用密钥的完整版本ID编写CREATE COLUMN MASTER KEY,从而创建一个COL使用UI的UMN ENCRYPTION KEY,然后使用Always Encrypted向导使用适当的密钥对指定的列进行加密。


I'm trying to setup a new Always Encrypted database using Azure Key Vault (I have previously had this working). In the SSMS Always Encrypted Wizard I can select the table and column to encrypt but I have a problem after selecting "Azure Key Vault" as the key store provider. I login and the window briefly pops up the dropdown that correctly lists my Key Vault in Azure but then it immediately goes away and has a warning triangle with the word "Purge" next to it and a "Try Again" button.

Clicking "Details" shows:

Any ideas what this means and how to get the wizard to complete?

I have tried this on 2 different installations of SQL 2016 with same result and using SSMS from different machines.

I know it says "We experienced issues in connecting to Azure" but since it is logging in and listing (briefly) my key vault what could the connection issue be?

Thanks.


Portion of details

===================================

We experienced issues in connecting to Azure (We experienced issues in connecting to Azure)

===================================

Purge (Microsoft.SqlServer.Management.ServiceManagement)


Program Location:

at Microsoft.SqlServer.Management.ServiceManagement.ResourceManagement.AzureKeyVaultKeyPermissionEnumConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list, JsonReader reader, JsonArrayContract contract, JsonProperty containerProperty, String id) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)

Adding SSMS Version details here:Microsoft SQL Server Management Studio 13.0.16106.4Microsoft Analysis Services Client Tools 13.0.1700.441Microsoft Data Access Components (MDAC) 10.0.15063.0Microsoft MSXML 3.0 4.0 6.0Microsoft Internet Explorer 9.11.15063.0Microsoft .NET Framework 4.0.30319.42000Operating System 6.3.15063

解决方案

I was able workaround this by creating the KEY in the vault, scripting out the CREATE COLUMN MASTER KEY referencing the key's full version ID from the vault, creating a COLUMN ENCRYPTION KEY using the UI then use the Always Encrypted wizard to encrypt the designated columns with the appropriate keys.

这篇关于始终使用Azure Key Vault SSMS清除错误加密的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-16 05:17