Connect .Net Core to Azure Key Vault in Ten Minutes

preview_player
Показать описание
Hey friends, In this video let's look at how to access secrets in an Azure Key Vault from a .Net Core web application. Azure Key Vault is a cloud-hosted service for managing cryptographic keys and secrets like connection strings, API keys, and similar sensitive information. Key Vault provides centralized storage for application secrets.

In this demo, we will add an API endpoint to drop a message into an Azure Storage Queue. We will store the connection string required to connect to the storage account in Key Vault and access it from there. We will also how to handle key rolling/rotation scenarios and gracefully update the application to use the new secret from Key Vault.

Рекомендации по теме
Комментарии
Автор

You have covered at least 16 hrs of billable effort in under 11 minutes. Great pace and more importantly quality content & thanks. I'm here after Scott Hanselman's tweet.

VinayKumar-queg
Автор

I love the pace.
It's short and to the point.
Exactly what I needed to share with my team.
Thank you Rahul!!

nitinmistry
Автор

Thank you Rahul, You are just producing what is needed for a developer, crisp, precise and to the point, saving many hours of R&D and efforts, God bless you.

adaamit
Автор

Excellent, Very straight forward and easy to understand

banam
Автор

Nice Rahul, Thanks for posting on AKV. keep the good work and posting of these tricky videos.

HimanshuMishra
Автор

you are always top of my search query . thanks rahul .

anowereng
Автор

i don't know how i should thank you for uploading such a quality content ..lots of love from my side ..

rishukumar
Автор

Happy to see your videos, The series on Azure Vault looks really impressive. I am exploring more of your videos. Could you please give an overall picture in the beginning like some diagram or explain in words the approach that we are going to have.

vikasviswan
Автор

Brilliant Rahul, you have explained it all so nicely. thanks really appreciate it

venkyv
Автор

It helped me to understand my environment :)

Автор

Great video, what's the best option to work with different environment? Let's say we have a connection string for Testing, another one for UAT and another one for Production.

holivieri
Автор

can you write a unit test case for keyvault?

dotnet
Автор

Won't using Polly this way cause the key-vault configuration to be reloaded from keyvault EVERY time there is a failure in sending message to queue ? I understand this may be set up like this just for illustration purpose, but I wonder what are the best practices for dealing with such issues.

iambhanu
Автор

I've you were using managed identities to access the storage account, couldn't you get remove the dependency on Key Vault altogether?

dandoescode
Автор

Can you please make more videos on .Net core web API like
Authentication and Authorization (Token based authentication and provide access to web API method basis on token)
Middleware
Dependency injection etc..
It helps lot.

deepakbasruru
Автор

Hi Rahul, I have my aspnet core application that pulls the connection string from KeyVault using Manage Identity. Currently the application is running in Azure App Service. Now i want to move this application to AKS. Will the application still works? Or i have to explore pod identity ?

skannan
Автор

Polly is Open Source. Any alternative for handling this?

rukminiverlekar
Автор

I followed the same steps that you mentioned but I am getting the error to get the token : DefaultAzureCredential failed to retrieve a token from the included credentials.
- EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
- ManagedIdentityCredential authentication unavailable. No Managed Identity endpoint found.

YadavTechs
Автор

please share the code. I did not understand how Azure authorized your app for the key-vault itself and gave you access to the keys ?!!

androidsavior
Автор

I am getting AKV10032 invalid issuer. Keyvaault exception here ☹️

rukminiverlekar