Support Visibility in Automate via Chef Server

[chris-rock]

Cookbook version

2.0

Scenario:

Customers use the latest version of Automate that allows users to send reports to Visibility Data Collector API via Chef Server. This increases security, since all requests are signed now. The audit cookbook should support that scenario

Solution

As discussed with @alexpop, we are two different endpoints that are being used based on the setup. We have the following flows:

1. chef-client (with dc_token) —> chef-server(/data-collector/) —> chef-automate authenticates using dc_token from client
2. chef-client —> chef-server(/organizations/ORG/data-collector) —> chef-automate authenticates using dc_token added by chef-server after verifying the client

The first flow is already implemented. We need to add support for the second flow.

• /data-collector/ requires dc_token
• /organizations/([^/]+)/data-collector requires chef signed headers

[chris-rock]

fixed via #163