In ASP.NET Core, WebApplication.CreateBuilder automatically includes the user secrets configuration source when the environment is set to . You can access these secrets using the standard Configuration API or the Options Pattern . Using IConfiguration:
To use user secrets, you must first initialize your project. This adds a UserSecretsId to your .csproj file, which maps your project to a specific folder in your local user profile. How to manage user secrets in ASP.NET Core
Adding them directly to the secrets.json file that opens after you select Manage User Secrets . Via .NET CLI: Use the set command to add individual keys: In ASP
Right-click the project in Solution Explorer and select Manage User Secrets . This adds a UserSecretsId to your
The tool in ASP.NET Core provides a safe way to store this information during local development by keeping it outside your project directory. 1. Enable Secret Storage
Once initialized, secrets are stored in a secrets.json file located in your user profile folder (e.g., %APPDATA%\Microsoft\UserSecrets\ on Windows or ~/.microsoft/usersecrets/ on macOS/Linux).
public class MyController : ControllerBase { private readonly IConfiguration _config; public MyController(IConfiguration config) => _config = config; public IActionResult Get() { var apiKey = _config["ServiceApiKey"]; // Retrieves the secret return Ok(); } } ``` ### Key Best Practices * **Development Only:** User secrets are **not encrypted** and are only intended for local development. * **Production Security:** Never use Secret Manager for production. Instead, use more secure providers like [Azure Key Vault](https://learn.microsoft.com/en-us/aspnet/core/security/key-vault-configuration) or [environment variables](https://microsoft.com). * **Source Control:** Ensure your `secrets.json` file path is never added to `.gitignore`, though it should already be safe since it lives outside the project folder. Use code with caution. Copied to clipboard How to manage user secrets in ASP.NET Core - InfoWorld
