On 11/08/16 13:46, Michael Hurn wrote:
> Sadly that was not the case as the auth.conf settings were correct.
> The log below is from when I take a look at the smartproxy and do a
> 'refresh' under 'Overview'.
auth.conf does indeed look correct, but the error seen by the smart
proxy is pretty clear:
> E, [2016-08-11T12:32:42.238822 #4126] ERROR -- : Failed to list puppet
> environments: Failed to query Puppet find environments v2 API: 403
> {"message":"Not Authorized: Forbidden request:
> vm-puppet.test.local(127.0.1.1) access to /v2.0/environments [find] at
> :119","issue_kind":"FAILED_AUTHORIZATION"}
I think you need to look at the Puppet master configuration in more
detail to find why it's being refused. This isn't the smart proxy itself.
Perhaps the auth.conf you're editing isn't the active copy, it's in
another path to what you're expecting for some reason, isn't loaded
(restart the master), or similar.
Dropping the Puppet master to a debug log level should show more
information about why it's not authorising access. That may require
setting log_level in the master's config.ru (or running it in the
foreground with --debug), and reconfiguring your syslog daemon to log
debug level messages.
--
Dominic Cleal
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
