Storing sensitive data like API keys, database connection strings, or passwords directly in your code or appsettings.json is a major security risk. If you accidentally commit these files to source control (like GitHub ), anyone with access to the repository can see them.
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 How to manage user secrets in ASP.NET Core
Right-click the project in Solution Explorer and select Manage User Secrets . Storing sensitive data like API keys, database connection
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). // Retrieves the secret return Ok()
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