why hard coded client secrets in json file or in code?? it will defeat the purpose of security .

What's the benefit here, previously connection string was my secret thing in appsettings, but now the key vault 'Secret' is a that secret thing.

This was an excellent tutorial, just straight to the point with everything needed without meandering...Thank you Jose.

@MeinGoogleAccount

Жыл бұрын

totally agree 🙂

Thank you. This is what I was looking for. Simple, step by step.... and working!

Thanks Jose! I just had to do this for a Microservices project I'm working on. Great tutorial and very easy to follow!

Thank you! I've been trying to get that working for a week and this is the first one I could follow.

Thank-you so much, I have been reading documentation all day trying to get this working on my app, your video helped so much!

Thanks a lot mate, I was struggling with KeyVault because the docs are a bit outdated. Your video saved me.

Very good video. I was doing this process accessing directly at the KeyVault API but as you show is simpler and faster to do it. Thank you Jose.

Great video, I found it much easier to understand thank other guides I watched!

You're really a cool teacher and i like your charisma too. Thx for video, helped me a lot.

Great explanation and concept coverage brother, keep up the good work. Thanks, Jose

Thanks bro, this video really saved me, I spent more than 2 weeks just to set up the keyvault without visual studio credentials. Finally your video gave me the solution. Really thank you so much.

Thanks Jose, loved the simplicity of explanation ❤❤❤❤

Spent a lot of time looking for the right answer, here it is. thanks!

This is the best video on Azure Key Vault usage. I subscribed to your channel. Please make more videos with examples. I appreciate you for your time and effort

Great video Jose, easily you explained with example...Great thanks

Great & many thanks from France for the tutorial !

Σε ευχαριστώ πολύ για το εξαιρετικό σου βίντεο!!!

Thanks. Your explanations are clear!

Very well explained, thank you!

This helped me SO much! Thank you!

Well explained, great tutorial

Thats a very genuine smile you have

very nice way to demonstrate azure key vault service really helpful thinking if I could follow the same method in azure function project

Good tutorial, just the answer I need.

You helped me a lot...thank you so much. I have just subscribed to your channel.

Great video. What has become apparent to me is that this approach (using client secrets) shoud only be used for a backend server, such as a microservice or any app that does not have any means to hit the public network or being accesible from the outside world, given we should not be storing any secrets in code/app setings for client facing apps. This solution fits my needs on this basis. Tested and working nicely. Thank you...

@charlesw.61

Жыл бұрын

Exactly... if you have an application that's client-facing and the tenantId, clientId, etc., is being stored in an Azure Library then this solution/approach is somewhat incomplete.

Thanks Joes... This video helped a lot...

very good and easy explanation

Great video!! Not sure I see how you specifically link your connection string to the DB context or whatever method you are using to connect to the azure database

@MrNoeLeiva

8 ай бұрын

do you have a git repo?

Well explained.

Subscribed!!!!

So if a developer tries to debug a C# code that reads the secret value then this will expose the secret right?

Hi, Its a good demonstration on how to consume secretes from azure key vault into a dotnet application. But here I have question. What this that we achieved here. For an hacker, even if he or she able to access the application client ID and client secrete, will then be able to read the key vault. My question is, how is this approach will make sure, that hackers will not be able to access our secretes.?

@VincentYang024

2 жыл бұрын

Absolutely agree, this would be considered as learning azk tutorial, not practical usage

@debasisdakhinaray3437

Жыл бұрын

In this case we can go for DefaultAzureCredential approach

Thanks bro!

Thanks was the on;ly video helpful . i got stuck at the last permission part this video helped me

Great video, thanks! One question - For dotnet 6.0 (have program.cs only, not startup.cs), what changes are required here where it calls for config.json keys? (example "defaultConenction" for conenctionString) How can I get azure key vault connectionString here: builder.Services.AddDbContext(options => options.UseMySQL(builder.Configuration.GetConnectionString("DefaultConnection"))); Any suggestions? Thanks :-)

Nice tutorial, could you please upload a video, to authenticate the application thru certificate under key vault?

Helpfull 😄

Thank you!

how the visual studio getting the connection string. I understand it is ocming form Azure key secret but in the prgome which code is saying this is the connection string that need to be used?

Please upload one video for Active Directory Authentication as well with an example.

Hello sir. What is easier key vault key, secrets, cert or using managed identity to authenticate to an app to sql?

can you explain how to manage different environment(dev,test,qa,production) connection string using keyvault and webapp

It is unclear how the mapping is happening between KV keyGroup--key_1 and ConfigGroup:Key_1, is there a default naming convention/behaviour?

How to get the secret with managed identity ? any samples

Any chance for an update on Core 6?... since Program.cs + Startup.cs combo are no longer a thing! :(

Hi Jose can you please help me, it is not accessing the connectionstring it is throwing error the error is: Microsoft.Data.SqlClient.SqlException: 'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)'

Hi do you have the source code and DB to test? thanks

Hi , how to integrate hashicorp vault in .net core and moving keyvaultname to appsetings thanks in advance

Hi, Thanks for the video, I clearly Understood, could you make a video how to make configurable TenentId, SecretId, Valut URL rather than storing in App.config file...

@mileshannahlane72

3 жыл бұрын

Thanks for great video Jose. I would also love a video of configurable TenentId, SecretId, Valut URL

Providing code would have been much better idea. Is this visual studio 2022?

I do not see mentioning "Secret key/name" anywhere in the config. Is it because you had only one secret you were able to retrieve it without referring the secret name?

@RAM-ff8dy

Жыл бұрын

I had the same doubt..

Hi Jose great video! Could you please share the source code?

Strangely as of now, Microsoft is still updating Microsoft.Extensions.Configuration.AzureKeyVault. Last publish was on Dec 15, 2021. And last publish for Azure.Extensions.AspNetCore.Configuration.Secrets was on May 19, 2021.

Need kubernetes interview questions..

tutorial for net framework ?

Good Tutorial, but please avoid annoying music

Everything is good except the background music.

This defeats the purpose of storing your secret on Azure. Anyone can run your application.

Very useful, thank you :)