
Explore app settings and secrets in ASP.NET Core, mastering five access methods, their priority, secure development across environments, and deploying secrets with Azure key vault.
Identify common application secrets in web apps, including connection strings, secure passwords, oauth client secrets, and third-party api keys, and learn strategies to protect them from development to production.
Secure app secrets to prevent exposure of payment gateway APIs, OAuth credentials, and database connection strings. Protecting secrets reduces liability and financial impact from data loss and disrupted sales.
Create a new ASP.NET Core MVC project in Visual Studio 2019, enable Razor runtime compilation, and explore the appsettings.json file within the standard MVC folders (models, views, controllers, wwwroot).
Publish the app settings manager to GitHub as source control, creating a private repository, pushing the initial commit, and preparing to log future lecture-specific changes.
Examine appsettings.json and add a SendGrid key section to store the secret for email sending. Retrieve this value in startup or controllers and display it in home controller index view.
Learn to access appsettings.json values with IConfiguration and dependency injection in ASP.NET Core, and retrieve the SendGrid key using GetValue<string>('SendGrid key').
Discover how to group Twilio credentials in a dedicated appsettings section and retrieve token and account SID via configuration in ASP.NET Core.
Learn how to pull values from app settings in ASP.NET Core using IConfiguration. Compare GetValue with GetSection to fetch Twilio auth token and ssid, and see why GetValue simplifies access.
Add a three-level nested section in appsettings.json, retrieve the bottom level value in the controller, and display it in the view, with next video covering alternative methods.
Learn how to read multi level settings from appsettings.json in ASP.NET Core by using GetSection and GetValue patterns, and display the third level setting in a view bag.
Inject IConfiguration into the view to access app settings, such as the Twilio section, using dot value to retrieve the auth token and account SID.
Learn to bind a Twilio settings class to the app settings section in an ASP.NET Core app, matching properties to keys and accessing them via configuration in controllers and views.
Configure and access app settings using IOptions in ASP.NET Core by binding the Twilio section to a settings class in Startup, enabling global dependency injection and cleaner access in controllers.
Move Twilio settings binding from the home controller to the startup class using dependency injection and IOptions, binding the Twilio section and registering TwilioSettings as a singleton.
Implement a generic extension method on IServiceCollection named add configuration to bind a T configuration section, instantiate T, apply options, and register the instance as a singleton.
Explore configuring social login settings in ASP.NET Core by binding Facebook and Google key/value pairs to a social login settings class, and compare options pattern, configure, and direct configuration retrieval.
Inject IOptions into views using the options pattern, define social login options, and access the Google key via social login options value in the view.
Define a connection string in the connection strings section of appsettings.json, retrieve it with GetConnectionString by key, and bind it for database configuration in ASP.NET Core.
Override default app settings with environment-specific files like appsettings.development.json and appsettings.staging.json, which take precedence over appsettings.json. Configure environments via launch settings and ASP.NET Core environment variables.
Protect development secrets with user secrets and the secret manager. Keep secrets out of appsettings.json and source control, stored per project in a plain text file under the user profile.
Learn to manage user secrets in ASP.NET Core by initializing and setting secrets with the dotnet user-secrets tool, and see how secrets override environment-specific appsettings in development.
Explore how environment variables in launchSettings.json override appsettings and secrets, including top-level keys and nested sections like Twilio using double underscores; refresh to apply changes.
Set environment variables in the console for an ASP.NET Core app with dotnet run, using user secrets and keys like SendGrid and Twilio, noting IIS Express scope.
Learn to add and manage environment variables on Windows for ASP.NET Core apps, including user versus system variables, and applying changes by restarting Visual Studio or the server.
Override app settings and secrets in ASP.NET Core with the command line, showing the five priority hierarchies and that command line has the highest priority, demonstrated at localhost 5001.
Customize the ASP.NET Core configuration by clearing the default builder and adding appsettings.json, environment-specific appsettings, user secrets (development only), environment variables, and command line.
Add a custom json file to ASP.NET Core app settings, configure its place in the settings hierarchy in Program.cs, and observe key precedence with user secrets.
Learn to securely store application secrets in production using Azure Key Vault, with managed identities, OAuth or certificate authentication, and robust access control.
Create an Azure key vault from the portal, configure a resource group, unique vault name, region, and access policies, then enforce environment isolation and networking settings for secure secrets management.
Publish the asp.net core app to azure app service for windows, create a resource group and a plan (free option). Then configure app settings and keys; user secrets stay local.
Learn to integrate Azure Key Vault with ASP.NET Core by installing configuration NuGet, wiring the URL, and loading secrets like SendGrid and Twilio on localhost with Azure CLI authentication.
Enable system assigned identity in the Azure app service and grant Key Vault read and list permissions to access secrets like SendGrid and phone numbers in production.
Move the key vault name to app settings and read it from the configuration provider in Program.cs by building the configuration, ensuring the Azure integration remains functional after publish.
Application Settings is a small piece of .NET Core application! But it is a very CRITICAL piece. Since you have all secrets and passwords.
Not knowing how to configure AppSettings would lead to a vulnerable application and it would be difficult to manage things once the application grows.
There are multiple ways to access your secrets in a .NET Core application, I will be walking you through all the ways in this course.
There is a certain hierarchy that is followed when it comes to a priority about which settings should be read first and knowing the correct order is critical. We will walk through all of that!
Losing control of production passwords, API keys, and other secrets can be extremely costly to any business. In this course, Securing Application Secrets in ASP.NET Core, you will learn how to keep secrets safe in development through to production.
This course will get you up and running with ASP.NET Core AppSecrets and Settings from basics all the way to completely securing them using Azure Key vaults.