History

Whit Waldo 55895fa19d Updated Dapr runtime/CLI version used in integration tests (#1485 ) * Updated itests.yml to use latest 1.15 runtime and CLI versions over 1.14 versions * Updated CLI argument name as `dapr-http-max-request-size` was changed in a recent update included in the CLI Signed-off-by: Whit Waldo <whit.waldo@innovian.net>		2025-03-16 20:14:32 -05:00
..
Properties	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
components	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00
Program.cs	Remove unused using statements. (#1313 )	2024-10-24 17:00:09 -05:00
README.md	Updated Dapr runtime/CLI version used in integration tests (#1485 )	2025-03-16 20:14:32 -05:00
SecretStoreConfigurationProviderSample.csproj	Remove .NET Core 3.1 support and standardize on .NET 6 (#1045 )	2023-08-24 11:04:02 -07:00
Startup.cs	replaced license headers (#802 )	2021-12-10 13:39:06 -08:00
secrets.json	SDK Docs (#572 )	2021-02-16 22:15:33 -08:00

README.md

Dapr secret store configuration provider in ASP.NET Core

Prerequisites

Overview

This document describes how to use the Dapr Secret Store Configuration Provider sample to load Secrets into ASP.NET Core Configuration.

To load secrets into configuration call the AddDaprSecretStore extension method with the name of the Secret Store and a list of secrets descriptors or related metadata.

Using the Dapr Secret Store Configuration Provider ASP.NET Core example

1. Use Dapr to run the application

Use Dapr to run the application:

dapr run --app-id SecretStoreConfigurationProviderSample --resources-path ./components/ -- dotnet run

2. Test the application

Run the following command in other terminal:

curl http://localhost:5000/secret

The response should read: "This the way"