On Wednesday 03 of August 2016 02:22:29 Abir wrote: > I don't think the Chef plugin can act as a proxy for the Chef server. I > don't believe that would be possible ( or very secure ). > > This diagram in the official manual will give you an > idea:https://theforeman.org/plugins/foreman_chef/0.3/chef.svg > > Foreman simply receives the results of a Chef run Through the handler and > verifies this information with the chef server. The communication between > the chef client and server remains unchanged.
You are correct. The Foreman chef plugin originally worked as endpoint for the client handler but it ignores authentication completely so you should always configure it to communicate through smart proxy (with smart proxy chef plugin). Rajnesh, what exactly does not work for you? You don't mention any error message. -- Marek -- 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.
