puppet-ca (8) Linux Manual Page
puppet-ca – Local Puppet Certificate Authority management.
Synopsis
puppet ca action
Description
This provides local management of the Puppet Certificate Authority.
You can use this subcommand to sign outstanding certificate requests, list and manage local certificates, and inspect the state of the CA.
Options
Note that any configuration parameter that’s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action. For example, server and run_mode are valid configuration parameters, so you can specify –server <servername>, or –run_mode <runmode> as an argument.
See the configuration file documentation at http://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 with –genconfig.
- –render-as FORMAT
- The format in which to render output. The most common formats are
json,s(string),yaml, andconsole, but other options such asdotare sometimes available. - –verbose
- Whether to log verbosely.
- –debug
- Whether to log debug information.
Actions
destroy–SYNOPSIS- puppet ca destroy
DESCRIPTION- Undocumented action.
- puppet ca destroy
fingerprint–SYNOPSIS- puppet ca fingerprint [–digest ALGORITHM]
DESCRIPTION- Undocumented action.
OPTIONS–digest ALGORITHM – The hash algorithm to use when displaying the fingerprint- puppet ca fingerprint [–digest ALGORITHM]
generate–SYNOPSIS- puppet ca generate [–dns-alt-names NAMES]
DESCRIPTION- Undocumented action.
OPTIONS–dns-alt-names NAMES – The comma-separated list of alternative DNS names to use for the local host. When the node generates a CSR for itself, these are added to the request as the desiredsubjectAltNamein the certificate: additional DNS labels that the certificate is also valid answering as. This is generally required if you use a non-hostnamecertname, or if you want to usepuppet kickorpuppet resource -Hand the primary certname does not match the DNS name you use to communicate with the host. This is unnecessary for agents, unless you intend to use them as a server forpuppet kickor remotepuppet resourcemanagement. It is rarely necessary for servers; it is usually helpful only if you need to have a pool of multiple load balanced masters, or for the same master to respond on two physically separate networks under different names.- puppet ca generate [–dns-alt-names NAMES]
list– List certificates and/or certificate requests.SYNOPSIS- puppet ca list [–[no-]all] [–[no-]pending] [–[no-]signed] [–digest ALGORITHM] [–subject PATTERN]
DESCRIPTION- This will list the current certificates and certificate signing requests in the Puppet CA. You will also get the fingerprint, and any certificate verification failure reported.
OPTIONS–[no-]all – Include all certificates and requests.- –digest ALGORITHM – The hash algorithm to use when displaying the fingerprint
- –[no-]pending – Include pending certificate signing requests.
- –[no-]signed – Include signed certificates.
- –subject PATTERN – Only include certificates or requests where subject matches PATTERN.
- PATTERN is interpreted as a regular expression, allowing complex filtering of the content.
- puppet ca list [–[no-]all] [–[no-]pending] [–[no-]signed] [–digest ALGORITHM] [–subject PATTERN]
print–SYNOPSIS- puppet ca print
DESCRIPTION- Undocumented action.
- puppet ca print
revoke–SYNOPSIS- puppet ca revoke
DESCRIPTION- Undocumented action.
- puppet ca revoke
sign–SYNOPSIS- puppet ca sign [–[no-]allow-dns-alt-names]
DESCRIPTION- Undocumented action.
OPTIONS–[no-]allow-dns-alt-names – Whether or not to accept DNS alt names in the certificate request- puppet ca sign [–[no-]allow-dns-alt-names]
verify–SYNOPSIS- puppet ca verify
DESCRIPTION- Undocumented action.
- puppet ca verify
Copyright And License
Copyright 2011 by Puppet Labs Apache 2 license; see COPYING