Vault as a Connect CA

Consul can be used with Vault to manage and sign certificates. The Vault CA provider uses the Vault PKI secrets engine to generate and sign certificates.

This page documents the specifics of the Vault CA provider. Please read the certificate management overview page first to understand how Consul manages certificates with configurable CA providers.

Requirements

Prior to using Vault as a CA provider for Consul, the following requirements must be met:

  • Vault 0.10.3 or later. Consul uses URI SANs in the PKI engine which were introduced in Vault 0.10.3. Prior versions of Vault are not compatible with Connect.

Configuration

The Vault CA is enabled by setting the ca_provider to "vault" and setting the required configuration values. An example configuration is shown below:

  1. connect {
  2.     enabled = true
  3.     ca_provider = "vault"
  4.     ca_config {
  5.         address = "http://localhost:8200"
  6.         token = "..."
  7.         root_pki_path = "connect-root"
  8.         intermediate_pki_path = "connect-intermediate"
  9.     }
  10. }

The configuration options are listed below. Note, the first key is the value used in API calls and the second key (after the /) is used if you’re adding configuring to the agent’s configuration file.

  • Address / address (string: <required>) - The address of the Vault server.

  • Token / token (string: <required>) - A token for accessing Vault. This is write-only and will not be exposed when reading the CA configuration. This token must have proper privileges for the PKI paths configured.

  • RootPKIPath / root_pki_path (string: <required>) - The path to a PKI secrets engine for the root certificate. If the path doesn’t exist, Consul will attempt to mount and configure this automatically.

  • IntermediatePKIPath / intermediate_pki_path (string: <required>) - The path to a PKI secrets engine for the generated intermediate certificate. This certificate will be signed by the configured root PKI path. If this path doesn’t exist, Consul will attempt to mount and configure this automatically.

  • CAFile / ca_file (string: "") - Specifies an optional path to the CA certificate used for Vault communication. If unspecified, this will fallback to the default system CA bundle, which varies by OS and version.

  • CAPath / ca_path (string: "") - Specifies an optional path to a folder containing CA certificates to be used for Vault communication. If unspecified, this will fallback to the default system CA bundle, which varies by OS and version.

  • CertFile / cert_file (string: "") - Specifies the path to the certificate used for Vault communication. If this is set then you need to also set tls_key_file.

  • KeyFile / key_file (string: "") - Specifies the path to the private key used for Vault communication. If this is set then you need to also set cert_file.

  • TLSServerName / tls_server_name (string: "") - Specifies an optional string used to set the SNI host when connecting to Vault via TLS.

  • TLSSkipVerify / tls_skip_verify (bool: false) - Specifies if SSL peer validation should be enforced.

Root and Intermediate PKI Paths

The Vault CA provider uses two separately configured PKI secrets engines for managing Connect certificates.

The RootPKIPath is the PKI engine for the root certificate. Consul will use this root certificate to sign the intermediate certificate. Consul will never attempt to write or modify any data within the root PKI path.

The IntermediatePKIPath is the PKI engine used for storing the intermediate signed with the root certificate. The intermediate is used to sign all leaf certificates and Consul may periodically generate new intermediates for automatic rotation. Therefore, Consul requires write access to this path.

If either path does not exist, then Consul will attempt to mount and initialize it. This requires additional privileges by the Vault token in use. If the paths already exist, Consul will use them as configured.

Vault ACL Policies

Vault Managed PKI Paths

The following Vault policy allows Consul to use pre-existing PKI paths in Vault. Consul is granted read-only access to the PKI mount points and the Root CA, but is granted full control of the Intermediate or Leaf CA for Connect clients.

In this example the RootPKIPath is connect_root and the IntermediatePKIPath is connect_inter. These values should be updated for your environment.

  1. # Existing PKI Mounts
  2. path "/sys/mounts" {
  3.   capabilities = [ "read" ]
  4. }
  6. path "/sys/mounts/connect_root" {
  7.   capabilities = [ "read" ]
  8. }
  10. path "/sys/mounts/connect_inter" {
  11.   capabilities = [ "read" ]
  12. }
  14. path "/connect_root/" {
  15.   capabilities = [ "read" ]
  16. }
  18. path "/connect_root/root/sign-intermediate" {
  19.   capabilities = [ "update" ]
  20. }
  22. path "/connect_inter/*" {
  23.   capabilities = [ "create", "read", "update", "delete", "list" ]
  24. }

Consul Managed PKI Paths

The following Vault policy allows Consul to create and manage the PKI paths in Vault. Consul is granted the ability to create the PKI mount points and given full control of the Root and Intermediate or Leaf CA for Connect clients.

In this example the RootPKIPath is connect_root and the IntermediatePKIPath is connect_inter. These values should be updated for your environment.

  1. # Consul Managed PKI Mounts
  2. path "/sys/mounts" {
  3.   capabilities = [ "read" ]
  4. }
  6. path "/sys/mounts/connect_root" {
  7.   capabilities = [ "create", "read", "update", "delete", "list" ]
  8. }
  10. path "/sys/mounts/connect_inter" {
  11.   capabilities = [ "create", "read", "update", "delete", "list" ]
  12. }
  14. path "/connect_root/*" {
  15.   capabilities = [ "create", "read", "update", "delete", "list" ]
  16. }
  18. path "/connect_inter/*" {
  19.   capabilities = [ "create", "read", "update", "delete", "list" ]
  20. }