Managing User Secrets

In this episode, Robert is joined by Andrew Cheung ( / andrewcmsft ) and Alicia Chan, who show how Visual Studio can help you stop storing sensitive data like connection strings and other user secrets in your code. They show how to store secrets locally in json or XML files and how to store them in Azure Key Vault.

[@shashirama2204]

Whats wrong??. confusing (jumping everywhere, too fast, no proper begin and end). Thank you Robert for asking them to show some details.

[@SeanMcDonnellIE]

This feature is really frustrating that the only option for a key vault is Azure. I work in a large company with literally 1000+ .NET developers. We don't use Azure. Most users only care about securing the contents of a config / appSettings. We want the equivalent of web.config encrypted sections in. NET core.

[@AhmedBaGaLaTy]

That exactly what we need, How to make it secret ? Any user still can get secret.json file from his local machine, and not encrypted!!
How to encrypt secret or appsettings files to make it secret :D ?

[@JeremyC]

What if we publish the project onto our own server? Does the Key Vault still work with a published project?

[@mrwuhaibei]

Demo is a bit confused. I was expecting to see the connection string display in the page. Because we want to approve the config value can be read from azure key vault service.

[@frankhaugen]

What is up with all of these web applications? How about a good old-fashioned desktop application? (console and/or WPF)

[@kbdavis0007]

How do you use this with non azure hosting providers?

[@DorianC]

Anyone know how to add a nested secret to Azure? For example if I have a secret called NestedSecret, but my azure app needs to access it through its parent, how can I do that in Azure?

[@samk7373]

and where will you store the secret of the Vault when you deploy to production?

[@AndyNicholson]

Sooooo, this doesn't work?
I did the same as you did, created a new project, went to "Manage User Secrets", create an entry and then try to use the "@config..." but errors with "the name config doesn't exist in the current context" and doesn't give me anything useful. Then you skipped straight on to Azure stuff, isn't there another part of the setup you've missed?
Really, really confused.

[@RonStack]

I'm experiencing the same thing. Have you found a solution?

[@edwardmullan2724]

You would have to initialise the Config object in the Startup class. This video: th-cam.com/video/m_BevGi7zBw/w-d-xo.html gives a good step by step.

[@SiegfriedFarnonMRCVS]

soooo badly explained...presenters not thinking at all what the user wants to see...Agree, the host did a good job of stopping them and getting them to explain..still really bad

[@AZ-bu7ss]

like for intro!!! and for episode of course

[@dotnetdevni]

Again forces us to use azure

[@saddlebear]

Kind of glossed over the "magic" of production and development credentials to access Key Vault.

[@dheeraj0076]

Poorly explained topic with lot of jumps around. If someone is reading and monitoring comments, please explain to these guys that someone would watch this presentations and viewers need to understand it rather than you guys show your skills of playing with your mouse and keyboard at lighting speed.

[@dotnetdevni]

This is only good for development though