将多个秘密存储在Azure密钥库中,并通过钥匙库从SQL DB链接服务访问它们
我在实现一个方案时被卡住了...
我需要通过钥匙库(存储在密钥库秘密中的连接字符串)连接Azure SQL DB。当整个SQL DB连接字符串存储为Secret时,我可以做同样的事情。 (服务器名称,数据库名称,用户名和密码),
但我的要求是.... 在我们的客户特定密钥保险库中,我们有SQL Server名称的单独秘密,SQL实例的另一个秘密,数据库名称的第三个秘密。 (现在连接字符串以不同的秘密分开)
如何将这些关键保险库秘密组合在一起并从中制成连接字符串?
第二要求我不想将用户名密码秘密存储,因为它不是由于安全目的而允许。
我面临的局限性。
- 在链接到Azure SQL DB通过钥匙保险库中,它要求秘密名称,我们可以一次阅读一个秘密。因此,如何通过密钥保险库摘要在Azure SQL DB链接服务中调用这些不同的秘密
:我在密钥库中有多个秘密,而不是整个连接字符串。如何将它们组合并连接到Azure SQL DB(我们这样做是因为根据客户服务器名称和实例名称更改,因此我们希望使其动态化),
请帮助答案。
I am stuck while implementing one scenario that...
I need to connect Azure SQL DB via key vault (connection string stored in key vault secret). I am able to do same when entire sql DB connection string is stored as secret. (server name, DB name, username and password)
But my requirement is....
In our customer specific key vault we have seperate secrets for Sql server name, Another secret for Sql instance , third secret for database name.
(Now connection string split in different secrets)
How to combine these key vault secrets and make connection string out of it?
second requirement is that I don't want to store username password in secret as it is not allowed because of security purpose.
Limitations which i have faced.
- in linked service to Azure sql DB via key vault it ask for secret name and we can read one secret at a time. so how to call these different secrets in Azure sql db linked service via key vault
Summary: I have multiple secrets in key vault instead of entire connection string. How to combine them and connect to Azure SQL DB ( We are doing this because as per customer server name and instance name changes so we want to make it dynamic)
Please help with answer.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
对不同的访问策略敏感,而其他具有正常访问权的敏感,
列出访问策略并将其零件存储在关键保险库中。
参考:
s01 , so2
sensitive with different access policy, and others with normal get,
list access policy and store their parts, in Key Vault as secrets.
References:
S01, SO2