View on GitHub

Arcus Security

Azure Security development in a breeze

Using secret store

As alternative to the usage of placing secrets into an IConfiguration instance in your application, the Arcus.Security.Core package provides a alternative concept called ‘secret store’.

We provide an approach similar to how IConfiguration is built, but with a focus on secrets. You can pick and choose the secret providers you want to use and we’ll get the job done!

Once register, you can fetch all secrets by using ISecretProvider which will get secrets from all the different registered secret providers.


For this feature, the following package needs to be installed:

PM > Install-Package Arcus.Security.Core


The secret stores are configured during the initial application build-up in the Program.cs:

public class Program
    public static void Main(string[] args)

        public static IHostBuilder CreateHostBuilder(string[] args) =>
                .ConfigureAppConfiguration((context, config) => 
                .ConfigureSecretStore((context, config, builder) =>
                    var keyVaultName = config["KeyVault_Name"];
                .ConfigureWebHostDefaults(webBuilder => webBuilder.UseStartup<Startup>());

Once the secret providers are defined, the ISecretProvider can be used as any other registered service:

public class HealthController : ControllerBase
    public HealthController(ISecretProvider secretProvider)

Built-in secret providers

Several built in secret providers available in the package.

If you require an additional secret providers that aren’t available here, please this document that describes how you can create your own secret provider.

← back