Skip to content

remilapeyre/vault-acme

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c3991e4 · Sep 25, 2022

History

35 Commits
Sep 25, 2022
Apr 22, 2022
Nov 22, 2019
Apr 22, 2022
Apr 22, 2022
May 5, 2020
Jul 23, 2020
Apr 22, 2022
Oct 26, 2019
Sep 25, 2022
Apr 22, 2022
Apr 20, 2022
Apr 20, 2022

Repository files navigation

Vault ACME

This plugin has not been properly reviewed and should not be used in production.

Vault ACME is a Vault secret engine that allow users and application to retrieve TLS certificates validated by an ACME provider like Let's Encrypt without having to give each applications permission to modify DNS and using Vault's audit and policy systems.

Discussion: hashicorp/vault#4950

Download Vault ACME

Binary releases can be downloaded at https://github.com/remilapeyre/vault-acme/releases.

Documentation

The documentation is available at website/source/docs/secrets/acme/index.html.md.

How to use this plugin

Using this plugin in Docker requires to manually set the mlock file capability to both Vault and the acme plugin:

$ sudo setcap cap_ipc_lock=+ep $(readlink -f $(which vault))
$ sudo setcap cap_ipc_lock=+ep /vault/plugins/acme-plugin

After setting plugin_directory and setting the correct shasum in Vault (vault write sys/plugins/catalog/secret/acme sha_256=$(sha256sum acme-plugin) command=acme-plugin) you can mount the plugin like any other: vault secrets enable -path acme -plugin-name acme plugin.

Tests

The unit tests will use the pebble ACME test server and pebble-challtestsrv. They can be downloaded at https://github.com/letsencrypt/pebble and must be present in $PATH.

The unit tests can be run with:

$ make test

The acceptance tests needs Vault in addition to pebble and pebble-challtestsrv.

When vault is present in $PATH the acceptance tests can be run with:

$ make testacc