- Manage certificates and requests
Standalone certificate authority. Capable of generating certificates, but mostly
used for signing certificate requests from puppet clients.
puppet cert action
[-h|--help] [-V|--version] [-d|--debug] [-v|--verbose]
Because the puppet master service defaults to not signing client certificate
requests, this script is available for signing outstanding requests. It can be
used to list outstanding requests and then either sign them individually or
sign all of them.
Every action except ´list´ and ´generate´ requires a
hostname to act on, unless the ´--all´ option is set.
- Revoke a host´s certificate (if applicable) and
remove all files related to that host from puppet cert´s storage.
This is useful when rebuilding hosts, since new certificate signing
requests will only be honored if puppet cert does not have a copy of a
signed certificate for that host. If ´--all´ is specified
then all host certificates, both signed and unsigned, will be
- Print the DIGEST (defaults to the signing algorithm)
fingerprint of a host´s certificate.
- Generate a certificate for a named client. A
certificate/keypair will be generated for each client named on the command
- List outstanding certificate requests. If
´--all´ is specified, signed certificates are also listed,
prefixed by ´+´, and revoked or invalid certificates are
prefixed by ´-´ (the verification outcome is printed in
- Print the full-text version of a host´s
- Revoke the certificate of a client. The certificate can be
specified either by its serial number (given as a hexadecimal number
prefixed by ´0x´) or by its hostname. The certificate is
revoked by adding it to the Certificate Revocation List given by the
´cacrl´ configuration option. Note that the puppet master
needs to be restarted after revoking certificates.
- Sign an outstanding certificate request.
- Verify the named certificate against the local CA
- Build an inventory of the issued certificates. This will
destroy the current inventory file specified by
´cert_inventory´ and recreate it from the certificates found
in the ´certdir´. Ensure the puppet master is stopped before
running this action.
Note that any setting that´s valid in the configuration file is also a
valid long argument. For example, ´ssldir´ is a valid setting,
so you can specify ´--ssldir directory
´ as an argument.
See the configuration file documentation at
https://docs.puppetlabs.com/references/stable/configuration.html for the full
list of acceptable parameters. A commented list of all configuration options
can also be generated by running puppet cert with ´--genconfig´.
- Operate on all items. Currently only makes sense with the
´sign´, ´list´, and
- Set the digest for fingerprinting (defaults to the digest
used when signing the cert). Valid values depends on your openssl and
openssl ruby extension version.
- Enable full debugging.
- Print this help message
- Enable verbosity.
- Print the puppet version number and exit.
$ puppet cert list
$ puppet cert sign culain.madstop.com
Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2.0 License