The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Remove the namespaceauth.conf file
|Assignee:||Henrik Lindberg||% Done:|
|Affected Puppet version:||Branch:||https://github.com/puppetlabs/puppet/pull/1204|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
To start puppet agent with —listen you need both the auth.conf and namespaceauth.conf. I don’t think the namespaceauth.conf is necessary anymore since it seems to do the same thing but less as the auth.conf (both badly named security files), so if that’s true get rid of it. Otherwise document it.
#2 Updated by John Kloian almost 6 years ago
It appears that currently the namespaceauth.conf file must exist, but it can be empty.
auth.conf on puppet client reads:
When trying to start puppet, log states:
Will not start without authorization file /etc/puppet/namespaceauth.conf
Touch /etc/puppet/namespaceauth.conf and puppet will run correctly and use ACLs as stated in auth.conf
#3 Updated by Matt Robinson about 5 years ago
- Assignee deleted (
I’m pretty certain that namespaceauth.conf is completely useless at this point, so probably need removal not documentation. I haven’t conclusively proven this and don’t have the time to do so right now, so I’m removing myself from the ticket.
#8 Updated by Nick Fagerlund almost 4 years ago
- Assignee set to Patrick Carlisle
So removal of the relevant code paths is merged into 3.x as of commit 4b6db1c6f3bb383d8309c5d98cb6236862caf085, but I notice the setting is still present in defaults.rb at about line 172.
Assigning to Patrick, since he did the recent deed and I think he currently knows the most about the status here.