autosign.conf file can allow certain
certificate requests to be automatically signed. It is only valid on the CA primary Puppet server; a primary server not serving as a CA does not
autosign.confallowlist 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
[primary server] section of
The default confdir path depends on your operating system. See the confdir documentation for more information.
autosign.conffile must not be executable by the primary server 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 primary server automatically signs certificate requests.
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, the
autosign.conf allowlist 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 allowlist, 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 allow incoming requests without needing to modify
To explicitly disable
false in the
server] section of the CA primary server's
puppet.conf, which disables CA autosigning even
autosign.conf or a custom
policy executable exists.