This little tool can issue certificates from Hashicorp Vault. Originally, it has been written to guarantee certificate refresh (which didn't happen sometimes using automatic refresh capabilities of various Vault-aware tools), but it comes handy in a lot of situations.

certissuer [global options]

where global options can be:

• --address | -A : Vault URL address (default: $VAULT_ADDR). Required.
• --token | -T : Vault token (default: $VAULT_TOKEN). Required.
• --cn | -C : common name used in issued certificate. Required.
• --pki | -P : PKI mount in Vault. Required.
• --role | -R : PKI role in Vault. Required.
• --ip | -i : add an IP-based Subject Alternative Name
• --alt | -a : add a DNS name-based Subject Alternative Name
• --ttl | -t : expiration duration. Sent to the server verbatim (default: 50h)
• --ssldir | -d : Directory to put certificates to (default: /etc/ssl)
• --no-verify | -k: Skips TLS verification while communicating to Vault (default: $VAULT_SKIP_VERIFY)
• --format | -n : Certificate format (see later). Default: "well-known"
• --help: shows help
• --version: shows version

Certissuer can emit certificates in formats suit their purpose: providing certificates for HAProxy is different than doing it for NGINX. You can prefer storing all the certificates in a shared directory, or you might want to do it just how Certbot does.

Therefore, certissuer provides three formats:

• well-known: every cert goes into its own directory, and each data goes into their own well-known file name. Eg. CA goes into ca.pem, leaf certificate goes into cert.pem, certificate and intermediate certs go to fullcert.pem, and private key goes to privkey.pem. This is the default.
• named: this format saves full certificate chain (leaf and intermediate certificates concatenated) into <CN>.pem, and private key goes into <CN>.key.
• haproxy: this format generates a single file called <CN>.pem, containing leaf and intermediate certificates, and private key concatenated together.

Open a ticket, perhaps a pull request. We support GitHub Flow. You might want to fork this project first.

Small utilities are not commonly gather large communities, but we still require that discursion should be civil. Therefore, we adapt Contributor Covenant's Code of Conduct for this project.

SPDX-License-Identifier: BlueOak-1.0.0 OR MIT

This software is licensed under two licenses of your choice: Blue Oak Public License 1.0, or MIT Public License.