Brice, Looks like I messed up testing the #5020 patch because the helper script I was using to start the puppetmaster was copying an overly permissive auth.conf in. This was a relic of when I was documenting the REST API and wanted to not have to worry about security rules. I was testing the 2.6.x branch without this auth.conf on a different machine, so that's why it looked like your branch introduced the permission problem.
So +1 to this patch. On Tue, Oct 26, 2010 at 3:13 AM, Brice Figureau <[email protected]> wrote: > This is strange because this authorization check is done way before the > catalog compilation terminus is involved (where my modification is). This is confused me too. I should've followed code to see how it could have gotten by the early authorization. > How did you perform your tests? Using curl to do the requests Using a script to start the puppetmaster (this is where my problem was) -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
