autosign.conf file can allow certain certificate requests
to be automatically signed. It is only valid on the CA Puppet
master server; a Puppet master not serving as a CA does not
autosign.confwhitelist but more complex to configure.
For more information, see the documentation about certificate autosigning.
Puppet looks for
$confdir/autosign.conf by default. To
change this path, configure the autosign setting in the
The default confdir path depends on your operating system. See the confdir documentation for more information.
autosign.conffile must not be executable by the master’s user account. If the
autosignsetting points to an executable file, Puppet instead treats it like a custom policy executable even if it contains a valid
autosign.conf file is a line-separated list of certnames or
domain name globs. Each line represents a node name or group of node names for which
the CA Puppet master automatically signs certificate
rebuilt.example.com *.scratch.example.com *.local
Domain name globs do not function as normal globs: an asterisk
can only represent one or more subdomains at the front of a certname that resembles
a fully qualified domain name (FQDN). If your certnames don’t look like FQDNs,
autosign.conf whitelist might not be effective.
autosign.conffile can safely be an empty file or not-existent, even if the
autosignsetting is enabled. An empty or non-existent
autosign.conffile is an empty whitelist, meaning that Puppet does not autosign any requests. If you create
autosign.confas a non-executable file and add certnames to it, Puppet then automatically uses the file to whitelist incoming requests without needing to modify
To explicitly disable autosigning,
= false in the
[master] section of the CA Puppet master’s
disables CA autosigning even if
autosign.conf or a custom policy executable