ExSecrets

App config secret manager for different providers.

Installation

Install by adding ex_secrets to your list of dependencies in mix.exs:

def deps do
  [
    {:ex_secrets, "~> 0.3.0"}
  ]
end

How it works

This library loads secrets on demand from APIs or files. For dotenv file, it is loaded at startup and saved in the cache. Secrets are encrypted when store in the cache with a master key generated at startup. Enables developers to access keys securely.

Key features include:

• FETCH and SET secrets.
• Key fetch throttling.
• Authentications with providers like Azure Keyvault and Google Secrets manager and token renewals.
• Catching of secrets.
• Default key options.
• You can configure multiple secrets and access from different providers.
• RESET and RELOAD secrets without shutting down your application.

Usage

Get a secret

Secrets are first fetched using system environment. If found thats the value that is used. For this, no configuration is required.

iex(1)> ExSecrets.get("FOO")
nil
iex(2)> System.put_env "FOO", "BAR"
:ok
iex(3)> ExSecrets.get("FOO")
"BAR"
iex(4)>

To overide secret fetch from system environment by default, Specify your own default provider.

iex(1)> ExSecrets.get("FOO")
nil
iex(2)> Application.put_env(:ex_secrets, :default_provider, :dot_env)
:ok
iex(3)> ExSecrets.get("FOO")
nil
iex(4)> System.put_env "FOO", "BAR"
:ok
iex(5)> ExSecrets.get("FOO")
nil
iex(7)>

Set Secret

You can set a new secret version using:

iex(20)> ExSecrets.set("TEST", "test", provider: :azure_key_vault)
:ok

Reset and Reload

To reset the secrets and reload, this will clear the cached values and reload doenv. For other providers, values will be fetched on demand.

iex(20)> ExSecrets.reset()
:ok

Supported Providers

You can configure:

• Dot env file
• Azure Keyvault
• Azure Managed Identity
• Google Secret Manager
• AWS Secret Manager

Provider Config

Azure KeyVault configuration:

  config :ex_secrets, :providers, %{
    azure_key_vault: %{
      tenant_id: "tenant-id",
      client_id: "client-id",
      client_secret: "client-secret",
      key_vault_name: "key-vault-name"
    }
  }

Using certificate. You can use client_certificate_path or client_certificate_string. See Azure keyvault provider section for more details

  config :ex_secrets, :providers, %{
    azure_key_vault: %{
      tenant_id: "tenant-id",
      client_id: "client-id",
      client_certificate_path: "/path-to/mycert.key",
      client_certificate_string: "base 64 encoded string of the cert",
      client_certificate_x5t: "x5t of the cert",
      key_vault_name: "key-vault-name"
    }
  }

Azure Managed Identity Configuration:

config :ex_secrets, :providers, %{
  azure_managed_identity: %{
    key_vault_name: "key-vault-name"
  }
}

Google Secret Manager

Using service account. You can use service_account_credentials or service_account_credentials_path. See Azure keyvault provider section for more details

  config :ex_secrets, :providers, %{
    google_secret_manager: %{
      service_account_credentials: %{
        "type" => "service_account",
        "project_id" => "project-id",
        "private_key_id" => "key-id",
        "private_key" => "-----BEGIN PRIVATE KEY-----...-----END PRIVATE KEY-----\n",
        "client_email" => "secretaccess@project-id.iam.gserviceaccount.com",
        "client_id" => "client-id",
        "auth_uri" => "https://accounts.google.com/o/oauth2/auth",
        "token_uri" => "https://oauth2.googleapis.com/token",
        "auth_provider_x509_cert_url" => "https://www.googleapis.com/oauth2/v1/certs",
        "client_x509_cert_url" => "https://www.googleapis.com/robot/v1/metadata/x509/secretaccess%40project-id.iam.gserviceaccount.com",
        "universe_domain" => "googleapis.com"
        },
        service_account_credentials_path: "/path-to/cred.json"
    }
  }

AWS Secret Manager:

Using secret access key. Using instance role is coming soon.

config :ex_secrets, :providers, %{
      aws_secrets_manager: %{
        access_key_id: "taccess_key_id",
        secret_access_key: "secret_access_key"
      }
}

Dotenv file:

config :ex_secrets, :providers, %{
  dot_env: %{path: "/path/.env"}
}