Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support for Azure.Storage.Blobs in ProtectKeysWithAzureKeyVault
See original GitHub issueWe are currently using
.AddDataProtection()
.PersistKeysToAzureBlobStorage(new Uri(blobUri))
.ProtectKeysWithAzureKeyVault(kv, keyVaultUri);
to enable scenarios like scale out and deployment swapping.
Currently PersistKeysToAzureBlobStorage and its package Microsoft.AspNetCore.DataProtection.AzureStorage depend on Microsoft.Azure.Storage.Blob. This aspect could also be implemented using Azure.Storage.Blobs.
In a similar way ProtectKeysWithAzureKeyVault and its package Microsoft.AspNetCore.DataProtection.AzureKeyVault depend on Microsoft.Azure.KeyVault. This aspect could also be implemented using Azure.Security.KeyVault.Keys.
As we understand the communication/versioning scheme these new libraries seem to be the way forward.
We would like to move to the new blob storage and key vault clients as well as Azure.Identity for all our MSI handling and would be happy if the data protection extensions could support that as well. Especially for new applications we would like to avoid the dependency on the “old” libraries.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
https://github.com/dotnet/aspnetcore/pull/18203
Oh just an update to the libraries we depend on? Yea, we can look at that for v5.