13 KiB
| title | author | description | manager | ms.author | ms.custom | ms.date | ms.prod | ms.technology | ms.topic | uid |
|---|---|---|---|---|---|---|---|---|---|---|
| Safe storage of app secrets in development in ASP.NET Core | rick-anderson | Learn how to store and retrieve sensitive information as app secrets during the development of an ASP.NET Core app. | wpickett | scaddie | mvc | 05/16/2018 | asp.net-core | aspnet | article | security/app-secrets |
Safe storage of app secrets in development in ASP.NET Core
By Rick Anderson, Daniel Roth, and Scott Addie
View or download sample code (how to download)
This document explains techniques for storing and retrieving sensitive data during the development of an ASP.NET Core app. You should never store passwords or other sensitive data in source code, and you shouldn't use production secrets in development or test mode. You can store and protect Azure test and production secrets with the Azure Key Vault configuration provider.
Environment variables
Environment variables are used to avoid storage of app secrets in code or in local configuration files. Environment variables override configuration values for all previously specified configuration sources.
::: moniker range="<= aspnetcore-1.1"
Configure the reading of environment variable values by calling AddEnvironmentVariables in the Startup constructor:
[!code-csharp] ::: moniker-end
Consider an ASP.NET Core web app in which Individual User Accounts security is enabled. A default database connection string is included in the project's appsettings.json file with the key DefaultConnection. The default connection string is for LocalDB, which runs in user mode and doesn't require a password. During app deployment, the DefaultConnection key value can be overridden with an environment variable's value. The environment variable may store the complete connection string with sensitive credentials.
[!WARNING] Environment variables are generally stored in plain, unencrypted text. If the machine or process is compromised, environment variables can be accessed by untrusted parties. Additional measures to prevent disclosure of user secrets may be required.
Secret Manager
The Secret Manager tool stores sensitive data during the development of an ASP.NET Core project. In this context, a piece of sensitive data is an app secret. App secrets are stored in a separate location from the project tree. The app secrets are associated with a specific project or shared across several projects. The app secrets aren't checked into source control.
[!WARNING] The Secret Manager tool doesn't encrypt the stored secrets and shouldn't be treated as a trusted store. It's for development purposes only. The keys and values are stored in a JSON configuration file in the user profile directory.
How the Secret Manager tool works
The Secret Manager tool abstracts away the implementation details, such as where and how the values are stored. You can use the tool without knowing these implementation details. The values are stored in a JSON configuration file in a system-protected user profile folder on the local machine:
Windows
File system path:
%APPDATA%\Microsoft\UserSecrets\<user_secrets_id>\secrets.json
macOS
File system path:
~/.microsoft/usersecrets/<user_secrets_id>/secrets.json
Linux
File system path:
~/.microsoft/usersecrets/<user_secrets_id>/secrets.json
In the preceding file paths, replace <user_secrets_id> with the UserSecretsId value specified in the .csproj file.
Don't write code that depends on the location or format of data saved with the Secret Manager tool. These implementation details may change. For example, the secret values aren't encrypted, but could be in the future.
::: moniker range="<= aspnetcore-2.0"
Install the Secret Manager tool
The Secret Manager tool is bundled with the .NET Core CLI in .NET Core SDK 2.1. For .NET Core SDK 2.0 and earlier, tool installation is necessary.
Install the Microsoft.Extensions.SecretManager.Tools NuGet package in your ASP.NET Core project:
Execute the following command in a command shell to validate the tool installation:
dotnet user-secrets -h
The Secret Manager tool displays sample usage, options, and command help:
Usage: dotnet user-secrets [options] [command]
Options:
-?|-h|--help Show help information
--version Show version information
-v|--verbose Show verbose output
-p|--project <PROJECT> Path to project. Defaults to searching the current directory.
-c|--configuration <CONFIGURATION> The project configuration to use. Defaults to 'Debug'.
--id The user secret ID to use.
Commands:
clear Deletes all the application secrets
list Lists all the application secrets
remove Removes the specified user secret
set Sets the user secret to the specified value
Use "dotnet user-secrets [command] --help" for more information about a command.
[!NOTE] You must be in the same directory as the .csproj file to run tools defined in the .csproj file's
DotNetCliToolReferenceelements. ::: moniker-end
Set a secret
The Secret Manager tool operates on project-specific configuration settings stored in your user profile. To use user secrets, define a UserSecretsId element within a PropertyGroup of the .csproj file. The value of UserSecretsId is arbitrary, but is unique to the project. Developers typically generate a GUID for the UserSecretsId.
::: moniker range="<= aspnetcore-1.1" [!code-xml] ::: moniker-end ::: moniker range=">= aspnetcore-2.0" [!code-xml] ::: moniker-end
[!TIP] In Visual Studio, right-click the project in Solution Explorer, and select Manage User Secrets from the context menu. This gesture adds a
UserSecretsIdelement, populated with a GUID, to the .csproj file. Visual Studio opens a secrets.json file in the text editor. Replace the contents of secrets.json with the key-value pairs to be stored. For example: [!INCLUDEsecrets.json file]
Define an app secret consisting of a key and its value. The secret is associated with the project's UserSecretsId value. For example, run the following command from the directory in which the .csproj file exists:
dotnet user-secrets set "Movies:ServiceApiKey" "12345"
In the preceding example, the colon denotes that Movies is an object literal with a ServiceApiKey property.
The Secret Manager tool can be used from other directories too. Use the --project option to supply the file system path at which the .csproj file exists. For example:
dotnet user-secrets set "Movies:ServiceApiKey" "12345" --project "C:\apps\WebApp1\src\WebApp1"
Set multiple secrets
A batch of secrets can be set by piping JSON to the set command. In the following example, the input.json file's contents are piped to the set command.
Windows
Open a command shell, and execute the following command:
type .\input.json | dotnet user-secrets set
macOS
Open a command shell, and execute the following command:
cat ./input.json | dotnet user-secrets set
Linux
Open a command shell, and execute the following command:
cat ./input.json | dotnet user-secrets set
Access a secret
::: moniker range="<= aspnetcore-1.1" The ASP.NET Core Configuration API provides access to Secret Manager secrets. Install the Microsoft.Extensions.Configuration.UserSecrets NuGet package.
Add the user secrets configuration source with a call to AddUserSecrets in the Startup constructor:
[!code-csharp] ::: moniker-end ::: moniker range=">= aspnetcore-2.0" The ASP.NET Core Configuration API provides access to Secret Manager secrets. If your project targets the .NET Framework, install the Microsoft.Extensions.Configuration.UserSecrets NuGet package.
In ASP.NET Core 2.0 or later, the user secrets configuration source is automatically added in development mode when the project calls CreateDefaultBuilder to initialize a new instance of the host with preconfigured defaults. CreateDefaultBuilder calls AddUserSecrets when the EnvironmentName is Development:
When CreateDefaultBuilder isn't called during host construction, add the user secrets configuration source with a call to AddUserSecrets in the Startup constructor:
[!code-csharp] ::: moniker-end
User secrets can be retrieved via the Configuration API:
::: moniker range="<= aspnetcore-1.1" [!code-csharp] ::: moniker-end ::: moniker range=">= aspnetcore-2.0" [!code-csharp] ::: moniker-end
String replacement with secrets
Storing passwords in plain text is risky. For example, a database connection string stored in appsettings.json may include a password for the specified user:
A more secure approach is to store the password as a secret. For example:
dotnet user-secrets set "DbPassword" "pass123"
Replace the password in appsettings.json with a placeholder. In the following example, {0} is used as the placeholder to form a Composite Format String.
The secret's value can be injected into the placeholder to complete the connection string:
::: moniker range="<= aspnetcore-1.1" [!code-csharp] ::: moniker-end ::: moniker range=">= aspnetcore-2.0" [!code-csharp] ::: moniker-end
List the secrets
[!INCLUDEsecrets.json file]
Run the following command from the directory in which the .csproj file exists:
dotnet user-secrets list
The following output appears:
Movies:ServiceApiKey = 12345
Movies:ConnectionString = Server=(localdb)\mssqllocaldb;Database=Movie-1;Trusted_Connection=True;MultipleActiveResultSets=true
In the preceding example, a colon in the key names denotes the object hierarchy within secrets.json.
Remove a single secret
[!INCLUDEsecrets.json file]
Run the following command from the directory in which the .csproj file exists:
dotnet user-secrets remove "Movies:ConnectionString"
The app's secrets.json file was modified to remove the key-value pair associated with the MoviesConnectionString key:
{
"Movies": {
"ServiceApiKey": "12345"
}
}
Running dotnet user-secrets list displays the following message:
Movies:ServiceApiKey = 12345
Remove all secrets
[!INCLUDEsecrets.json file]
Run the following command from the directory in which the .csproj file exists:
dotnet user-secrets clear
All user secrets for the app have been deleted from the secrets.json file:
{}
Running dotnet user-secrets list displays the following message:
No secrets configured for this application.