all Technical posts

Making the Secret Store More Powerful in Arcus Security v1.4

With this new version of Arcus.Security v1.4, the secret store has a ton of new updates. In this post we'll run over some of the major ones, but keep in mind this post will not contain all the new changes, so for more information see the release notes of this new version.

With the latest version of Arcus.Security v1.4, the secret store has a ton of new updates. In this post we’ll run over some of the major updates, keep in mind we won’t cover all of the new changes, so for more information see the release notes of this new version.

We assume you are familiar with some of the concepts of Arcus, especially the secret store concept. If you are not, we recommend reading our blog post, which will guide you through concept, or check out our official docs.

Secret name mutation

One of the most requested features shipped in this release is the mutation of secret names. When a secret is looked up in the Arcus secret store, the requested name is directly passed along to all the registered secret providers. The secret name mutation feature allows you to manipulate the secret name before it’s passed to the secret provider.

Imagine that you have two secret providers, the first one gets secrets from the IConfiguration (in Debug mode) and second from environment variables:

Values in the configuration are usually structed by using colons (ie. Arcus:Secrets:MySecret) while environment variables are mostly structured with capitals with underscores (ie. ARCUS_SECRETS_MYSECRET). But when requesting the secret, I would want to use the same name to request the same secret (in this case MySecret). Let’s say I want to use dots instead of colons or underscoes to requests secrets (as in Arcus.Secrets.MySecret). We can use the secret name mutation to mutate the secret name to adhere to the respectively secret provider’s secret name specifications before it’s passed along:

With these secret name mutations, we can call in secretProvider.GetRawSecret("Arcus.Secrets.MySecret") and it will correct the secret name so it matches the secret provider’s specifications.

Named secret providers

In certain scenarios, you may want to retrieve a secret from a specific secret provider without trying every other registered provider, just in case you already know the location of your secret.

In any case, you’ll have to interact in a different way with the secret store. That’s where this new feature comes into play.

Starting from v1.4, we allow secret providers to be registered with a unique name. This name will be used to later retrieve the provider so choose wisely. The environment variable secret provider can, for example, be registered with the name "EnvironmentVariables":

Normally, you would now inject the ISecretProvider into your dependent services to consume secrets. However, in order to retrieve a specific provider you need to inject ISecretStore which allows you to interact with the secret store.

By using our .GetProvider methods, you can now retrieve the previously registered environment variables secret provider directly by using its name.

A good example of why you would want to use this is our Azure Key Vault provider. With this latest release, you can store secrets in your vault. In order to be able to do that, you need to create a named secret provider so that you can store those secrets.

Critical exceptions

In version v1.3, when a secret was retrieved from the secret store and some authentication problem occurred, the secret store would incorrectly fail with ‘Secret not found’ exceptions. The secret store was not yet smart enough to know that some failures would need to be bubbled up to the consumer instead of swallowed into general ‘Secret not found’ exceptions. This problem also occurs when consumers want to implement their own secret provider and want the possibility to fail with custom exceptions. Previously, any problem that occurred in the internal registered secret providers would be notified incorrectly as ‘Secret not found’.

In the v1.4 release, we have fixed this problem by introducing the ‘Critical exceptions’ concept. This allows you to register certain exception types with or without certain predicates to determine if a thrown exception can be considered critical and should be notified to the end consumer. This functionality allows the creators of secret providers to register their own custom exceptions when they need it, and allows the existing secret providers to notify authentication problems while retrieving secrets.

See how these critical exceptions can be registered in the secret store:

Note that our existing secret providers (Azure Key Vault, …) already have been updated to include some critical exceptions. So when you register the Azure Key Vault or other built-in secret providers via .AddAzureKyVault... these exceptions will already have been added. This is also a take-away when you develop your own secret provider and want some exceptions that are considered critical with your provider register.


Besides these three major updates, we also have a lot of other stuff added to this release. Here are some take-aways:


This new version allows users more freedom to use Arcus secret store in real-life projects. It’s a responsible concept that makes sure that we make a distinct separation between configuration and secret values. With all these new features, we hope that users are even more convinced to give our Arcus security library a go.

If you have any questions, remarks, comments, or just want to discuss something with us; feel free to contact us. Thanks for reading!

Subscribe to our RSS feed

Thanks, we've sent the link to your inbox

Invalid email address


Your download should start shortly!

Stay in Touch - Subscribe to Our Newsletter

Keep up to date with industry trends, events and the latest customer stories

Invalid email address


Great you’re on the list!